Slow update of Access tables

  • Thread starter Thread starter Robert
  • Start date Start date
R

Robert

Hi all,

I'm developing a SW in VB6 that writes to an Access 2003 table while
another SW (set up as a Windows Service) is reading the same table and
erasing the records as they're read. I noticed a lapse of about 1 sec.
between writing and reading and I think this is due to a delay caused
by Access. Has anyone come across this problem? Is it resolvable?

Otherwise, could the same thing be done using a shared memory space
somewhere? How could it be developed considering there's two different
softwares running and using it simultaneosly?

Thanks,

Robert
 
Robert said:
Hi all,

I'm developing a SW in VB6 that writes to an Access 2003 table while
another SW (set up as a Windows Service) is reading the same table
and erasing the records as they're read. I noticed a lapse of about
1 sec. between writing and reading and I think this is due to a
delay caused by Access. Has anyone come across this problem? Is it
resolvable?

Otherwise, could the same thing be done using a shared memory space
somewhere? How could it be developed considering there's two
different softwares running and using it simultaneosly?
Click to expand...

This is a VB.Net ("dotnet") group. Though... The article from the local MSDN
library is not online @ MSFT anymore but I found it somewhere else:
http://doc.ddart.net/mssql/sql2000/html/mdacxml/htm/wpmigratingmiscellaneous.htm

Look for the headline "Refreshing the Cache" and how it's done with DAO and
ADO.


Armin
 
I'm developing a SW in VB6 that writes to an Access 2003 table while
another SW (set up as a Windows Service) is reading the same table and
erasing the records as they're read. I noticed a lapse of about 1 sec.
between writing and reading and I think this is due to a delay caused
by Access. Has anyone come across this problem? Is it resolvable?
Click to expand...

It's stuff like this that gives VB developers a bad name (not to mention
the OP doesn't konw the diff between VB/VB.NET ;-)!

Access is not a real database and it shouldn't be used in a multi-user
environment... there are better technologies for that sort of thing (i.e.
SQL Server Express)
 
Back
Top