Flushing the Jet / OleDB

  • Thread starter Thread starter Erik Visser
  • Start date Start date
E

Erik Visser

In one of my apps i use an access database via OLEDB and that goes well at
many
customers sites but not on one. There the problem is that sometmes added
rows disapear after closing the programm and restarting. The jet file is on
the network, the app too and there is only one user.
And ofcourse the problem cannot be reproduced.
I have told them to update the Jet and MDAC drivers and the Netware client
and to disable all kind of cache.
Now i wonder, is there a way to force to write to the file (more than a
commit transaction) ?

tia,

Erik
 
Erik said:
the problem is that sometmes added
rows disapear after closing the programm and restarting. The jet file is on
the network, the app too and there is only one user.
And ofcourse the problem cannot be reproduced.
I have told them to update the Jet and MDAC drivers and the Netware client
and to disable all kind of cache.
Now i wonder, is there a way to force to write to the file (more than a
commit transaction) ?
Click to expand...

Worth a try:

"'Jet OLEDB:Transaction Commit Mode Connection Property': In Microsoft
Jet 2.x and earlier, all writes were immediately committed. With Win32
and multi-threading, Microsoft Jet introduced a lazy-write mechanism.
Setting this property to a value of 1 causes all transaction commits to
be written immediately to disk for that Connection object. All other
Connection objects are unaffected."

http://support.microsoft.com/default.aspx?scid=kb;en-us;240317

Jamie.

--
 
Thanks Jamie, i think this will do.

Erik

Jamie Collins said:
Worth a try:

"'Jet OLEDB:Transaction Commit Mode Connection Property': In Microsoft
Jet 2.x and earlier, all writes were immediately committed. With Win32
and multi-threading, Microsoft Jet introduced a lazy-write mechanism.
Setting this property to a value of 1 causes all transaction commits to
be written immediately to disk for that Connection object. All other
Connection objects are unaffected."

http://support.microsoft.com/default.aspx?scid=kb;en-us;240317

Jamie.
Click to expand...
 
M'DB isn't reliable enough to be deployed to end users.

Use Access Data Projects it is a lot easier to deal with.. from the
drivers side of the equation.

ADP is bigger, better, faster for data entry / reporting and it's
easier during development

sprocs made mdb obsolete
i mean; duh-- you're stuck in the 90s.

-Aaron
ADP Nationalist
 
Back
Top