Not really sure where to post this question, because I'm not sure if it is a code issue, controls, or table problem. I'm not having a problem with reports or queries running..................yet.
I am expecting the forms to open right away, but there is a measureable pause.
I have recently created this database. It has very few records in it, so far.
The tables are indexed and "properly related" to each other.
I have Option Explicit in all of the modules and subs.
I ran the Performance wizard and fixed all of the suggestions.
There are a few combo boxes on each form and some listboxes. The rowsources of the listboxes are not "fixed", but are loaded by a button or other event.
It is split with the front end on my hard drive and the backend follows this path:S:\Info Systems\Fin Apps Team\Project Task Listing\TaskTracker_be.mdb.

Any thoughts?

How busy is the server on which the back end database is located? Is there a less busy time to access the database, in other words?

I'm not really sure how busy it is, but I can try to use it at different times of the day.
Would making the path shorter make any difference?

I understand from things I have read in the past that a shorter path works best with a Web server. I don't know if it would help your situation or not. However, it couldn't hurt to try it.

In addition to Franks suggestion:

Subdatasheet Name property set to [None] for all table in the back end

Track name AutoCorrect
Tools >> Options >> General >>.Track name AutoCorrect info should be off.


Also see:
Microsoft Access Performance FAQ