Plateforme Level Extreme
Abonnement
Profil corporatif
Produits & Services
Support
Légal
English
Order in fpt file entries
Message
De
25/09/2008 13:17:49
Calvin Smith
Wayne Reaves Computer Systems
Macon, Georgie, États-Unis
 
 
À
25/09/2008 09:07:06
Hilmar Zonneveld
Independent Consultant
Cochabamba, Bolivie
Information générale
Forum:
Visual FoxPro
Catégorie:
Codage, syntaxe et commandes
Versions des environnements
Visual FoxPro:
VFP 9 SP2
OS:
Vista
Network:
Windows 2008 Server
Database:
MS SQL Server
Divers
Thread ID:
01349628
Message ID:
01350670
Vues:
20
It broke. Would not reindex. Would not pack. Reported corrupted or missing fpt file. The file has 2 fields - acctnum and memo. Once the fpt file goes bad how do you reconnect the memo data to the correct acctnum unless the memo data also has a reference to the memo? With just a few records it is possible but this particular file has 7000 records with data going back to 1998. To me the weakest point of the entire FoxBase,FoxPro,VFP environment has always been memo fields. In most of my applications, I ghost write memo field entries into text files or some other mechanism so that I can programatically replace data when VFP decides the the fpt file is broken. I also take car to open memo file, get data, and then close them. I do not keep them open unless absolutely necessary. In this case, I was able to locate the broken records - about 40- and reinsert the data from a backup. However, I had to delete the existing records and then recreate them. At the end of this this tedious process the *((&*(() file would not pack - missing or corrupt fpt file! So , I did what I should have done at first- create a new file and read all the good records into it and then manually recreate the ones that would not transfer.
A problem is a problem only as long as it has a possible solution. Lacking that, it becomes a FACT!
Précédent
Suivant
Répondre
Fil
Voir

Click here to load this message in the networking platform