Form slow to open

[davesmith202]

When I clicked Create blank Form or try to just go to design view in my unbound form, it takes forever to load, maybe 20-30 seconds. Why?

The front end is on my desktop, with the backend on the server, which is about 90MB in size. I am using Access 2007.

Is it anything to do with it trying to drag in the field list for all tables?

Any ideas?

Thanks,

Dave

 

[Pat Hartman]

Extreme slowness can be caused by Access not being able to talk to your default printer. To see if this is the problem, go to the control panel and change your default printer to the Microsoft default or a PDF writer or fax. Anything that is not on a server. If that solves the problem, you can look into what is causing the problem with the printer being "offline" when Access is trying to talk to it.

If that didn't solve the problem, try compact and repair. Then try rebuilding the app in a clean database by importing all objects. Don't forget to set the start up properties and set any necessary references.

 

[davesmith202]

Thanks for the suggestions Pat. I've already compacted and repaired the front and backend. I tried the printer thing and that didn't solve it. However, I have discovered precisely the moment it happens.

If everybody else is logged out of the database, the an existing Form goes from design view to form view and backwards fairly quickly. But, the moment you open a form that shows data in another PC on the network, it immediately slows so that it takes about 1 minute to go from one view to the next. The instant you close the form showing data on another PC, it stops hanging on my PC and goes to design or form view.

Note that this is not a problem when the other PC just has the switchboard open, which only displays command buttons. So it seems to only happen when a form with data is showed. Incidentely, the form that was opened on the other PC has lots(!) of fields on it, if that makes any difference.

Any further thoughts given this additional information?

 

[gemma-the-husky]

might be an issue with not having a persistent connection to the backend (assuming it is shared and/or on a server)

you might try designing against a copy of the backend on your local PC, and releasing it the production environment after making your changes

 

[davesmith202]

Brilliant idea Dave! I was just thinking about putting the front end on the server and developing on there but your idea is far superior.

One issue I had with the linked table manager was that when I tried to update the location of the tables, it was asking me for the file location of each individual table, rather than just doing it in bulk. Is that a bug or something? I would have anticipiated I could just click select all and update them in one go.

 

[gemma-the-husky]

which version of access. I think A2003 probably does them one at a time. A2007/A2010 does it in bulk, I think.

To be honest, I think most of us do it in code. either use a file browser to pick the back-end, or store the target backend in a text file, and reconnect the tables with a simple bit of code. It makes the process much more professional

Search for one of the many back-end updater utilities

 

[Pat Hartman]

NEVER, NEVER, NEVER update objects in a database when others are using it. You the developer, need your own personal copy of the front end (actually everyone needs their own copy). You make changes in your copy, test them, and then distribute new copies of the FE to the users. Older versions of Access allowed this behavior but newer versions will not allow it unless you are using a code management add-in such as SourceSafe.

The linked table manager can only link to one BE at a time. If your FE links to multiple BEs (this includes spreadsheets), you need to be careful when you select tables to only select tables from one source at a time.

 

[davesmith202]

I am using Access 2007 and since there are about 30 tables, it would be extremely slow to update each table link manually, one at a time. Can I just delete the tables and then go External Data > Access and link to the tables that way? Or will deleting the tables and linking again like that delete some other aspects?

Pat, I am only updating my front end which is not used by anyone else. Everybody has their own front end.

I am only linking to one BE but there are so many tables. It is asking to link to each table individually, rather than just pointing to the BE and updating all at the same time. :S