Corrupt data

[william humphrey]

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.

On Mon, Apr 21, 2014 at 9:06 AM, william humphrey
<bill at bluewatermaritime.com> wrote:
> I dumped the data as SQL choosing UTF8 and using vStudio in the
> Windows environment and tried that and it still didn't work.  Do you
> have any suggestions on what to try, assuming that LiveCode in Windows
> sees the encoding of the data differently? I'm also getting odd
> corruption of the database after opening it in LivecCode -- the
> database then opens in vStudio but none of the tables are visible. So
> LiveCode in the Windows environment also does something to damage the
> database.
>
> On Mon, Apr 21, 2014 at 3:18 AM, Ruslan Zasukhin
> <ruslan_zasukhin at valentina-db.com> wrote:
>> On 4/16/14, 9:23 PM, "Mark Schonewille" <m.schonewille at economy-x-talk.com>
>> wrote:
>>
>>> Hi,
>>>
>>> The situation is the following. My customer sends me a database and a
>>> LiveCode project. Both of us have installed the latest version of
>>> Valentina. He is using Mac and I am using Windows.
>>>
>>> When I run the liveCode project, the scripts open the database and
>>> display data (mostly) in text fields. Unfortunately, the data appears
>>> corrupted. It looks like binary with lots of empty lines.
>>>
>>> The problem is not an encoding problem. If it were an encoding problem,
>>> I should see at least a few recognisable characters and probably most of
>>> the text would be readable, if it were just an encoding problem. Much
>>> more, it looks like an encryption problem, except that the data isn't
>>> encrypted.
>>>
>>> If I open the database in Valentina Studio and run a few queries,
>>> everything seems fine.
>>>
>>> Who has seen this before?
>>>
>>> If you have seen this before, how did you solve the problem?
>>
>> Hi Mark,
>>
>> Well, if Vstudio shows data correctly, then inside of db all is right.
>>
>>
>> Then really only case I see -- decoding from UTF16 to single-byte format,
>> which Livecode understands.
>>
>> I guess this is LOCAL DB, without vserver ...
>>
>>
>>
>> --
>> Best regards,
>>
>> Ruslan Zasukhin
>> VP Engineering and New Technology
>> Paradigma Software, Inc
>>
>> Valentina - Joining Worlds of Information
>> http://www.paradigmasoft.com
>>
>> [I feel the need: the need for speed]
>>
>>
>> _______________________________________________
>> Valentina mailing list
>> Valentina at lists.macserve.net
>> http://lists.macserve.net/mailman/listinfo/valentina
>
>
>
> --
> http://www.bluewatermaritime.com



-- 
http://www.bluewatermaritime.com