Plateforme Level Extreme
Abonnement
Profil corporatif
Produits & Services
Support
Légal
English
FoxDos 2.6, VFP memo problems
Message
De
19/10/2001 14:42:12
Ken Zak
Hagerty Classic Insurance
Traverse City, Michigan, États-Unis
 
 
À
18/10/2001 14:19:01
Information générale
Forum:
Visual FoxPro
Catégorie:
Problèmes
Divers
Thread ID:
00570429
Message ID:
00571064
Vues:
25
Hi Keith,

I had this very same problem. We would have 200-300 memo's dissapear in one day, work fine for another month or two and then again another 200-300 would disappear.

We had to do the following to fix the problem. Create a new table, append from the original and then recreate the CDX. This seemed to have solved the problem. At least we have not had a reoccurance in several months.




>I would appreciate any ideas regarding the following mysterious problem:
>
>I have inherited a VFP application that interacts with a FOX DOS application. It saves its data by stuffing it in the memo fields of the FOX DOS tables. It stores multiple 'fields' in one memo by using XML-like tags.
>
>Intermittantly users will get the following: They save data to the DOS memo fields, then return to find it has disappeared completely. This happens about 2-3 times a month, under fairly heavy use. Sometimes the pointer of the memo field in question seems to be corrupt (i.e. pointing somewhere past the end of the .fpt file) but not always. I haven't been able to reproduce the problem or even identify any pattern to the occurances.
>
>Another intermittant problem: The dreaded C0000005 error comes up now and then, again without any clear pattern to it. I did take care to make sure all objects are cleaned-up properly, but this didn't seem to help.
>
>The user workstations are Windows 98, accessing the .exe and data over a LAN, using the Microsoft client.
>
>
>Do you think that concurrent access by FOX DOS and VFP to the same table and memo could be a root cause of these problems, or should I look elsewhere?
>
>Thanks in advance for any ideas.
Précédent
Suivant
Répondre
Fil
Voir

Click here to load this message in the networking platform