Access performance

[Ilja Mihailovs]

My enterprise uses custom application written by a external
company. The executable connects to an Access database. The application is
NOT designed in a Access itself, it only uses it as a database. Everything
(including executable and a DB) is stored in a share on a server. Two users
simultaneously are working with the executable (launching it from a share).
Executable works with the DB, so to me it is no use in splitting the DB. One
user has extremely good response times (data is extracted quite fast). In
controversy, second user has to wait 1-2 minutes for the data to appear. Both
PCs are configured in the same way, no differences there.

Can someone suggest any share / DB tuning approach?

I believe DB splitting is none of use here.

 

[Jerry Whittle]

Make sure that both users have Read, Write, Create, and Delete privileges to
the folder holding the Access .mdb or .accdb files. Not just the files but
the entire folder.

Try temporarily disabling the virus checker on the machine having problems
and see if that helps. If so you could set it up to not scan .md* and .acc*
files.

On the flip side, maybe the slow computer is already infected with something
using up cpu and network access....

Then there is always the possibility of something like a weaker PC or
problems with the network connection.

 

[AccessVandal via AccessMonster.com]

I think Jerry covers lots of details there. You might want to do a compact
and repair the Back-end database if you have a Full version of access
installed in the shared machine.

Do a back of your Back-end first before you do a compact and repair. Check
the Back-end file size also. We don't know what your custom application do
that might cause your Back-end to bloat or or slow down or how it access the
data or the custom application somehow can't shared with two users. You might
to place the custom application in each Users PC if it has a custom Back-end
linker if it is possible. If it's not possible, I have no idea.