Access to slow after splitting!

J

JOM

I splict my database and it became so slow, I thought splitting it made it
more faster, any suggestions?

OJ!
 
D

Dirk Goldgar

JOM said:
I splict my database and it became so slow, I thought splitting it
made it more faster, any suggestions?

OJ!
Click to expand...

Splitting doesn't necessarily make it faster, but it shouldn't make it
significantly slower, either. Were you running it as a single .mdb file
on a network server before? Do you now have the back-end database in
the same server folder as before, and the front-end on your local PC?
Have you turned off the Name AutoCorrect option in the front-end
database?
 
A

Albert D.Kallal

I splict my database and it became so slow, I thought splitting it made it
more faster, any suggestions?
Click to expand...

Well, some parts might run better, as the forms, code etc now resides on
your pc. However, now that 'connection' exists between the front end file
(on your computer) and the back end file (in that shared folder), then
sometimes there is a BIG delay as the connection occurs.

To remove, or get rid of this delay, try keeping a persistent connection.
This simply means at program startup in the FE, you open a table in the back
end, and KEEP THIS table open. In fact, you can just open a table, and them
minimize it to 'test' this trick. Now, with that table minimized, try
running your application, and you will see speed has returned to un-split
levels.

This trick, and a few others can be found at:
http://www.granite.ab.ca/access/performancefaq.htm

By keeping the back end opened at all times, the re-connection dealy is
removed.
 
Top