G
Guest
Hi,
I have a VC++ DLL, which is inturn being used by a VB app. This VC++
DLL uses DAO to connect to a DB, which is an MS Access 97 DB. Now, at
times (usually when the size of the Access DB crosses 70MB), when I
fire a DELETE query on the DB (using DAO->Execute), the application
crashes. I use BeginTrans and CommitTrans on the DB in order to
maintain atmocity of transactions (the Execute call is between these two
transaction calls). Upon using a debugger (WinDbg), I figured
out that the crash occurs either just after a call (that is to say that the
control does not return back after these calls) to DaoDatabase->Execute() or
DaoDatabase->DaoWorkspace->CommitTrans(). The worst part is that there is no
DAO or any kind of exception that's thrown.
Is it some kind of a problem with Access 97, due to the size or some other
reason? I have spent too much time trying to find out the cause but to no
use. Thus, any kind of advice/suggestion/comment will help me a lot.
Thanks a ton in advace,
Ankit
I have a VC++ DLL, which is inturn being used by a VB app. This VC++
DLL uses DAO to connect to a DB, which is an MS Access 97 DB. Now, at
times (usually when the size of the Access DB crosses 70MB), when I
fire a DELETE query on the DB (using DAO->Execute), the application
crashes. I use BeginTrans and CommitTrans on the DB in order to
maintain atmocity of transactions (the Execute call is between these two
transaction calls). Upon using a debugger (WinDbg), I figured
out that the crash occurs either just after a call (that is to say that the
control does not return back after these calls) to DaoDatabase->Execute() or
DaoDatabase->DaoWorkspace->CommitTrans(). The worst part is that there is no
DAO or any kind of exception that's thrown.
Is it some kind of a problem with Access 97, due to the size or some other
reason? I have spent too much time trying to find out the cause but to no
use. Thus, any kind of advice/suggestion/comment will help me a lot.
Thanks a ton in advace,
Ankit