How to avoid refreshing linked tables

[RobinAG]

Hello all,

I have a front and back end to my database. The back end holds only tables, while the front end holds all forms, reports, queries and modules, with links to all the tables in the BE. For some reason the FE is going really slow, it's been suggested that maybe I'm having my tables refreshed too often. I haven't explictly put in the code anywhere to refresh the tables, so I'm wondering if it happens automatically, and if so, at what frequency and how I can either disable it entirely, or set so that it only updates tables when the table has been edited.

[MMcCarthy]

Hello all,

I have a front and back end to my database. The back end holds only tables, while the front end holds all forms, reports, queries and modules, with links to all the tables in the BE. For some reason the FE is going really slow, it's been suggested that maybe I'm having my tables refreshed too often. I haven't explictly put in the code anywhere to refresh the tables, so I'm wondering if it happens automatically, and if so, at what frequency and how I can either disable it entirely, or set so that it only updates tables when the table has been edited.

Firstly, I have moved your post to the Access forum. You mistakenly posted in the articles area.

Secondly, I don't believe that the problem is your tables refreshing unless you have code explicitly doing so.

There are a number of other areas to be looked at.

Is the network connection between the frontend and backend database running slow. To test this try just opening a table in data view on the frontend and see if there is any delay.

If there isn't then try running one of your saved queries and see if there is any delay there.

If neither of those things is causing a problem then you will need to look at the code behind your forms. Are you using a lot of recordsets or preforming a lot of operations in the form load events.

As for the reports have you got some fields declared as memo fields? These are notorious for slowing down reports.

[RobinAG]

Sorry about the mistake in posting.

I checked my network connection, it is indeed slow. Even when I place the front and back ends into the same folder, performance barely increases.

The forms do indeed have quite a bit of onload, oncurrent and onopen operations, and they have multiple subforms on them (3-5). On top of that, the main form I have problems with is an unbound form that fills in all the fields based on where it is accessed from. I know that can be a slow operation. This at times created slowdowns before I split the database into front and back ends; since the split, it has become unbearable for users.

I don't want to go back to one database for data safety reasons and filesize, but it sounds like I may have to rebuild big parts of the DB in order to set it up to give me front end speed.

Firstly, I have moved your post to the Access forum. You mistakenly posted in the articles area.

Secondly, I don't believe that the problem is your tables refreshing unless you have code explicitly doing so.

There are a number of other areas to be looked at.

Is the network connection between the frontend and backend database running slow. To test this try just opening a table in data view on the frontend and see if there is any delay.

If there isn't then try running one of your saved queries and see if there is any delay there.

If neither of those things is causing a problem then you will need to look at the code behind your forms. Are you using a lot of recordsets or preforming a lot of operations in the form load events.

As for the reports have you got some fields declared as memo fields? These are notorious for slowing down reports.

[MMcCarthy]

Try putting a copy of the frontend on the local machine and just leave the backend on the network. See if that helps any.