Home > Software engineering >  Why VB6 when debugging the source code, the project from the running state to exit status, project c
Why VB6 when debugging the source code, the project from the running state to exit status, project c

Time:09-26

Why VB6 when debugging the source code, the project from the running state to exit status, project calls to ACCESS Data. The Data in the MDB auxiliary file Data. The LDB exists, unless the closure VB6,
And the project of the generated EXE files exits, Data. LDB file immediately disappear automatically,

Excuse me, what is the reason, the former project debugging, the midpoint of the main form in project close button after exit the debug state, why the Data. The LDB file exists, the

There are Data. MDB and Data. What's the relationship between LDB.

CodePudding user response:

Microsoft Access database file. The MDB after open, the lock file to prevent open library files repeated errors

CodePudding user response:

reference 1st floor bakw response:
Microsoft Access database file. The MDB after opening the lock file, prevent double open library files an error

Thank you, that why finish testing, lock file exists,

CodePudding user response:

It should be your file have closed

CodePudding user response:

Close the connection after will not
If you are directly to stop debugging
Or with end to end, there might be no release

CodePudding user response:

May be no Close database statement in your program, therefore, although after debugging the program ended, but the database is not closed, so will the Data. The LDB file still exists, the solution is in the use of the database must be closed after the database objects: such as the Close
  • Related