Results 1 to 3 of 3
  1. #1
    Join Date
    May 2015
    Posts
    1

    Answered: Corrupt vfp 8.0 dbf file

    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!

  2. Best Answer
    Posted by elliottkerr

    "1. Open the dBase command line from the Windows Start menu.

    2. Log into the local dBase software with your username and password.

    3. Click on the dBase command line section of the window that is open.

    4. Type "dbf /recover yourDbaseFile.dbf" into the command line, where "yourDbaseFile.dbf" is the name of the dBase file whose tables are corrupted.

    5. Press "Enter." dBase takes some time (ranging from a few minutes to a few hours, depending on the size of the database) to analyze and repair the file and its contents. You are alerted when this process is finished.

    6. In case nothing of this can't help you, then you may apply for an assist to professional online service dedicated for crashed .dbf files https://onlinefilerepair.com/en/dbf-repair-online.html DBF files Online repair service"


  3. #2
    Join Date
    May 2015
    Posts
    1
    Provided Answers: 1
    1. Open the dBase command line from the Windows Start menu.

    2. Log into the local dBase software with your username and password.

    3. Click on the dBase command line section of the window that is open.

    4. Type "dbf /recover yourDbaseFile.dbf" into the command line, where "yourDbaseFile.dbf" is the name of the dBase file whose tables are corrupted.

    5. Press "Enter." dBase takes some time (ranging from a few minutes to a few hours, depending on the size of the database) to analyze and repair the file and its contents. You are alerted when this process is finished.

    6. In case nothing of this can't help you, then you may apply for an assist to professional online service dedicated for crashed .dbf files https://onlinefilerepair.com/en/dbf-repair-online.html DBF files Online repair service

  4. #3
    Join Date
    Nov 2002
    Posts
    128
    Provided Answers: 1
    "I can't figure out what VB would be doing to cause this problem."

    I have VB.Net applications using a legacy VFP data 'backend' with no problem at all.

    Assuming that this VB program usually runs just fine and generally does Not corrupt the VFP data table, then the problem is most likely Not the VB program itself.

    One likely cause could be network reliability/integrity.
    If you should be having intermittent network issues, and that should occur when the VFP table is open, that would very likely introduce corruption into the table.

    You say that the scheduled VB task runs every minute, but is it run from a single source or from multiple sources possibly conflicting with each other at times.

    If you have both the VFP code and the VB code in-house, I might suggest that you modify your approach to provide a better fault-tolerant situation, but it most likely would take some programming on both sides (or maybe only 1 side).

    Good Luck,
    JRB-Bldr

Posting Permissions

  • You may not post new threads
  • You may not post replies
  • You may not post attachments
  • You may not edit your posts
  •