B
Bruce Acciavatti
I've split a rather large Access2000 database that resides on a network
drive, by keeping the back-end on the network drive and placing the
front-end on the client's hard drive, linked to it. Both front-end and
back-end dbs are then compacted to save space.
This is a normal procedure, but when I run the database now it performs
much, much slower than the old unsplit version of the database, which is
unacceptable. I have had to back off this to the unsplit version of the
database, but it makes it difficult to install changes to the application
this way. I've never seen anything like this before. There are only 5
clients. All clients have Windows XP-Professional, and are running MS Office
2000.
One other thing, is that I tried putting the front-end on one system that is
running MS Office 2003 (and Access2003), and it works beautifully! Should I
try to have Office2003 installed on all the client machines, or is there
something else going on?
drive, by keeping the back-end on the network drive and placing the
front-end on the client's hard drive, linked to it. Both front-end and
back-end dbs are then compacted to save space.
This is a normal procedure, but when I run the database now it performs
much, much slower than the old unsplit version of the database, which is
unacceptable. I have had to back off this to the unsplit version of the
database, but it makes it difficult to install changes to the application
this way. I've never seen anything like this before. There are only 5
clients. All clients have Windows XP-Professional, and are running MS Office
2000.
One other thing, is that I tried putting the front-end on one system that is
running MS Office 2003 (and Access2003), and it works beautifully! Should I
try to have Office2003 installed on all the client machines, or is there
something else going on?