by Help required on the problem.
Machine Config:
Win 95, VB 6 and FoxPro/Clipper DB 2.5
The FoxPro database is accessed by 2 programs on the same machine. A VB program and a Foxpro program. If the VB program updates a row in the database and then the foxPro program tries to modify/update the row, it gives an error saying DBFNTX Error/1210 Corruption detected.
The error window has 2 buttons, Quit and Default. If quit is pressed, the program just quits and does nothing to the DB. If Default is pressed, then the program updates the colums of the table, just the way it is supposed to do.
On seraching the MSDN lib, it says that it is a known bug and Microsoft has solved it in Win NT 3.51 and had patches for Win NT 3.5. But, there is no mention of Win 95.
If the whole application is run on a Win NT machine, the VB application runs accessing the foxpro DB, but the FoxPro application doesn't run.
If the VB application Modifies a column in the FoxPro database and all the applications accessing the DB are closed, and an Index is created on the DB and then the foxpro applicaiton is made to modify the the Database, then the error message does not pop up when the change is done. If, the VB program again updates the columns of the DB, and the FoxPro program also updates the sames rows, the error message again pops up.
Indexing the FoxPro DB from the VB program after updating the columns does not help as Indexing requires the exclusive access of the DB.
How to solve the problem.
With regards,
Praveen