By using this site, you agree to our updated Privacy Policy and our Terms of Use. Manage your Cookies Settings.
424,495 Members | 1,110 Online
Bytes IT Community
+ Ask a Question
Need help? Post your question and get tips & solutions from a community of 424,495 IT Pros & Developers. It's quick & easy.

Access 2000 Split Database Performance issues.

P: n/a
After splitting a database into the standard "Front end" " Back End"
set-up the performance on the database has deteriorated to an unusable
/ unacceptable level - this occured as soon as the database was split.

I'm using access 2000 SP3.

When the database is run as a single combined database the performance
is absolutly fine.

Has anyone come across any issues like this and could point me in the
direction of a fix ?

Thanks in Advance.

Dave Willock
IT Development.
Nov 12 '05 #1
Share this Question
Share on Google+
1 Reply


P: n/a
Dave, visit Tony Toews' site at:
http://www.granite.ab.ca/accsmstr.htm

His "Performance" page has a number of good suggestions on how to tackle
this.

--
Allen Browne - Microsoft MVP. Perth, Western Australia.
Tips for Access users - http://allenbrowne.com/tips.html
Reply to group, rather than allenbrowne at mvps dot org.

"Dave Willock" <da*********@hotmail.com> wrote in message
news:13**************************@posting.google.c om...
After splitting a database into the standard "Front end" " Back End"
set-up the performance on the database has deteriorated to an unusable
/ unacceptable level - this occured as soon as the database was split.

I'm using access 2000 SP3.

When the database is run as a single combined database the performance
is absolutly fine.

Has anyone come across any issues like this and could point me in the
direction of a fix ?

Thanks in Advance.

Dave Willock
IT Development.

Nov 12 '05 #2

This discussion thread is closed

Replies have been disabled for this discussion.