Plateforme Level Extreme
Abonnement
Profil corporatif
Produits & Services
Support
Légal
English
Corrupt memos
Message
De
19/12/1997 13:34:00
 
 
Information générale
Forum:
Visual FoxPro
Catégorie:
Autre
Titre:
Divers
Thread ID:
00067084
Message ID:
00067252
Vues:
20
>>We've recently been getting lots of corrupt memos. Specifically, what's
>>happening is that when a user adds a memo, it sometimes acts as if all
>>previous memos are getting deleted. When I BROWSE the table, Memo appears
>>in the BROWSE as opposed to memo, indicating the VFP thinks there is
>>data there. But when I Ctrl+PgDn, nothing is displayed.
>>
>>There are two things that I suspect are causing this to happen:
>>
>>1. Corrupt data. I'm currently running FoxFix.
>>2. Netware drivers. We recently upgraded all desktops to Win95.
>>This is about the same time that the corruption started. The
>>Netware drivers are Intranetware Client 2.2.0.0. Has anyone
>>heard of problems using these drivers with Fox???
>>
>>
>>Also, if anyone has any other ideas that I can look at, let me know.
>
>I had this problem that was a bear to figure out. My problem that the pointer from the .DBF to the corresponding place in the .FPT was screwed up. Pack and Pack Memo did not help. To fix it, I opened the table and did a COPY TO TEMPFILE (WITH CDX), verify the contents of the TEMPFILE, close and delete original .DBF and .FPT. Then rename all the TEMPFILE components. IF your table is linked to a .DBC, then I would ZAP original then APPEND FROM TEMPFILE in order to maintain all your table properties.


We ran FoxFix. It found some problems with decimals, but not with pointers to memos.
This problem surfaced when we moved to Win95 about 2 weeks ago. Is there a problem
with VFP and the Intranetware drivers?
Craig Berntson
MCSD, Microsoft .Net MVP, Grape City Community Influencer
Précédent
Suivant
Répondre
Fil
Voir

Click here to load this message in the networking platform