Plateforme Level Extreme
Abonnement
Profil corporatif
Produits & Services
Support
Légal
English
SAVE TO MEMO vs SELECT memo field
Message
De
13/10/2010 00:33:29
 
 
À
12/10/2010 23:59:03
Information générale
Forum:
Visual FoxPro
Catégorie:
Codage, syntaxe et commandes
Versions des environnements
Visual FoxPro:
VFP 9 SP1
Divers
Thread ID:
01485183
Message ID:
01485191
Vues:
44
Thank you Tore,

Good suggestion but it isn't practical because there are more than 300 sites with over 1000 data sets. We are creating a new version with many new capabilities but it needs to work seamlessly with old data, so I need to understand the cause of the problem.

I am using a new machine (Windows 7, 64 bit) and the free tables date back to FoxPro DOS 2.6. Fox did ask me what the Code Page was before opening the table and I answered 437 or at least I should have. I wonder if there is some complication or mistake.

How is Southwest Fox going? Best wishes,

Alex





>I suggest that you use a binary memo field for this data.
>
>>A free table has a memo field that contains an array stored with SAVE TO MEMO. A cursor is created from some of the records in the free table.
>>
>>When compared, the corresponding memo fields in the table and cursor are the same, but if the array is RESTORE FROM MEMO from the table and the cursor, some but not all of the array elements are different between them, specifically some of the decimal values. I suspect this may be caused by something like different code pages for the free table and cursor.
>>
>>Does anyone have any suggestions?
>>
>>TIA,
>>
>>Alex
Précédent
Répondre
Fil
Voir

Click here to load this message in the networking platform