AW: Corrupt data

[Tiemo Hollmann TB]

Is there any explanation for that behavior?
For years the encoding didn't worked without this encoding.
Is it a change in LC 6.6 or a change in Valentina 5.5?
Tiemo

> -----Ursprüngliche Nachricht-----
> Von: Valentina [mailto:valentina-bounces at lists.macserve.net] Im Auftrag von
> Mark Schonewille
> Gesendet: Freitag, 25. April 2014 13:20
> An: Valentina Developers
> Betreff: Re: Corrupt data
> 
> Yep, that (without specifying the encoding) seems to work.
> 
> --
> Best regards,
> 
> Mark Schonewille
> 
> Economy-x-Talk Consulting and Software Engineering
> Homepage: http://economy-x-talk.com
> Twitter: http://twitter.com/xtalkprogrammer
> KvK: 50277553
> 
> Installer Maker for LiveCode:
> http://qery.us/468
> 
> Buy my new book "Programming LiveCode for the Real Beginner"
> http://qery.us/3fi
> 
> LiveCode on Facebook:
> https://www.facebook.com/groups/runrev/
> 
> On 4/21/2014 18:27, william humphrey wrote:
> > For anyone following this we found the solution -- we had the
> > following lines of code in our open database handler:
> >
> >      if the platform is "Win32" then
> >
> >              get VDatabase_IOEncoding( gtheDatabase, “Latin1“ )
> >
> >           else if the platform is "MacOS" then
> >
> >              get VDatabase_IOEncoding( gtheDatabase, “Macintosh” )
> >
> >           end if
> >
> > It turns out that "Latin1" is something that the database does not
> > like.  I commented it out and now it works perfectly. Interestingly
> > you can copy a valentina database right across from the Mac
> > environment to the Windows server without doing anything special and
> > it works just fine.
> >
> 
> _______________________________________________
> Valentina mailing list
> Valentina at lists.macserve.net
> http://lists.macserve.net/mailman/listinfo/valentina