Slow database: On error goto

[DajTwo]

I have a front end - back end database in testing now and when ever there are more than one user on the database, everything is very slow.

I am in the process of following the 100 tips to accelerate a database found on this forum and I have a question to reduce the number of lines of code.

On command buttons to load menus, is the On error goto process required for each of the command buttons?.

I read that I can use hyperlynks and hide forms to upload them early in the process but since the release date is near, I would like to explore this idea.

Thanks in advance.



If I did not say it before, I really appreciate the time and expertise of the users on this forum.

 

[MajP]

Error checking is not required, but it is always a good idea. I do not think you want your users to get the debug window and get into the back end code. However, if I am 100% certain I can not throw an error I will be lazy and not put in error checking. However, this will have nothing to do with the speed of your app. In the 100 tips look at the top 10 first. Normally these solve 90% of your problems. What version of Access. I would suggest these from that document

1. keep a persistent connection to your backend
2. turn off the track name auto correct
3. remove any subdatasheets in your tables

 

[DajTwo]

Thanks for the reply. I use Access 2003.

I already did the subdatasheet and the track name auto correct.

What is a 'persistent' connection?

If I did not say it before, I really appreciate the time and expertise of the users on this forum.

 

[MajP]

To create a persistent connection to the backend. Make a table with a single text field, and a single record. In your front end link to this table. Make a form and and bind it to this table. The form does not have to have anything on it. When you open the database place code to open this form hidden and then open your main form. You never see this form because it is hidden, but it is always open. In that way you always have a persistent connection to the backend. This was extremely important in A2K, but I do not think it makes a difference in A2003.