P
Patrick Fryer
Hi,
I'm doing some work on a project which involves accessing a large
Access database (about 850Mb)
The problem is when I'm doing an update/insert into the database the
oleDbCommand.executeNonQuery() method seems to return before Access has
committed the change - This means that a display I have on screen
which reads back what has just been 'inserted' doesn't work
correctly.
At first the problem was only intermittent but as the database has
grown it seems to happen all the time. It does work okay if I step
through the program in Visual Studio (thus introducing an artificial
delay). Does anyone know a way around this? Someway for the code to
block until the operation has been committed? I can't seem to find
info about this online. If I make the thread sleep for 500 MS after
performing the insert it's okay as well?
Is there a connection string parameter or something I can use? Our
customer wants to stick with MS Access for now although they want to
upgrade to SQL Server later.
Thanks. Patrick.
I'm doing some work on a project which involves accessing a large
Access database (about 850Mb)
The problem is when I'm doing an update/insert into the database the
oleDbCommand.executeNonQuery() method seems to return before Access has
committed the change - This means that a display I have on screen
which reads back what has just been 'inserted' doesn't work
correctly.
At first the problem was only intermittent but as the database has
grown it seems to happen all the time. It does work okay if I step
through the program in Visual Studio (thus introducing an artificial
delay). Does anyone know a way around this? Someway for the code to
block until the operation has been committed? I can't seem to find
info about this online. If I make the thread sleep for 500 MS after
performing the insert it's okay as well?
Is there a connection string parameter or something I can use? Our
customer wants to stick with MS Access for now although they want to
upgrade to SQL Server later.
Thanks. Patrick.