Foxpro dbf file

[lelandklein]

We have a visual basic 6.0 program that updates a FoxPro table through odbc. We have a timer program that starts up every minute to print reports from an action.dbf. Whenever we run a procedure in our program we are opening the tables that we use and then close them. I don't know what happens but sometimes I get an error message whenever we try to open the dbf that the VB program updated. The message is *.dbf has been corrupted. The table will need to be repaired before using again. We have a repair program that we use to fix the dbf file and the repair message says File EOF mark adjusted! (VFP8+). The only thing the VB program is doing is setting a logical field to either true or false. I can't figure out what vb would be doing to cause this problem. Ant help would be appreciated.

Thanks!

 

[JrClocker]

It's been a while since VB 6.0 (late 1990s?)...I didn't think there was any support for that anymore!

Without knowing all of the specifics, the sort of thing you described is usually do to 1 of 2 things:

1.) The mapping of the database in the code is not complete (i.e. a field is missing)
2.) You are not "closing" the database when you are done with it

 

[magellan]

Foxpro is that a derivative of Foxbase? If it is I'm amazed they're still around.