Reading the thread from Social.Technet (post 25), this seems to be a widespread problem yet I have not seen it on Ac2010. You say you have been developing this DB and these forms for a while. Is there any chance that at least one of the forms has a VERY large number of controls on it? (That includes things on a TAB control.) Or, if not now, has it had over 700 controls on it non-simultaneously - as in "deleted a control, replaced it or converted it to something else"?
I'm going to suggest an experiment that might be tricky, but it might also pinpoint something. When you have this REALLY slow form opening (the ones that take over 30 seconds), set up this situation.
Using your Remote Desktop setup, prepare to do testing for the case where the FE being run is physically on the same machine as its BE file.
Start Task Manager and switch to the "Processes" display. Normalize the window so that you can see some of your desktop.
Open your database. Normalize the window (if possible) so that you can see TM and your DB at the same time on your desktop.
Now launch one of the "ugly" forms. (Note: To figure out all of this, you might have to do this more than once.)
Immediately use the Task Manager as follows: Click in the CPU, Disk, and Network columns to identify the highest users of those resources. Also click the Memory, though I'm not betting on that one being an issue. Since your FE and BE are on the same machine, your Network load should be fairly low.
Switch Task Manager to "Performance" and look for peak usage in each of those categories. You want to identify whether you have tripped over a bottleneck somewhere. TM will show you broad-brush ideas of where you are eating resources.
From your Windows "Start" button (lower left corner), Click, scroll to Windows Adminstrative Tools, expand that, and start Resource Manager.
Again, while trying to load one of your stubborn forms, start it and switch to RM. In the menu, you can focus on CPU, Disk, Network, Memory, or the Overview screen. You want to see which files your task is hitting and how hard.
I'm trying to find out whether, when this craziness hits, you are disk-bound, network-bound, or CPU-bound. In a "normal" profile I would expect a brief burst of disk activity that might be too quick to see in detail (though Task manager's performance page DOES keep a history of the past several seconds). Then you would have a burst of network activity alternating with or parallel to CPU activity. Resource Monitor might tell you that the "network socket" you are using goes through the Loopback connection because the BE is on the same machine with the FE.
In a well-behaved system, those CPU and Network bursts would also be short-lived. In your case they might not be. It would also be interesting to know whether the CPU hog was MSACCESS itself or the ACE engine in a separate thread. In a brief load, you might not be able to see that, but for something running very long, RM might call it out separately. The trick here is to figure out what is working hardest.
