Performance

louiserome

Registered User.
Local time
Today, 02:01
Joined
May 22, 2001
Messages
14
I am currently developing quite a large company database. I have read a few posts that indicate that it is better to keep a few regularly loaded forms open as apposed to closing them. What is the best way as I have developed mine to always close them as i have always been lead to believe that having a number of windows open at the same time can cause your machine to crash.

Any advice would be greatly appreciated.
 
I'm new with Access but here are my thoughts on your subject....

I would suggest that in these days of faster machines with more RAM that the multi-tasking approach of having several forms open together fits the users requirements better.
However, that said, some people do prefer a clean-cut, one thing open at a time approach... it really depends on the user...

Have you thought about:

- Setup shortcut keys, menus and buttons to open key forms

- Allowing the user to close/open forms that they need (and leave them open if they want) thus customising their own workspace?

- Introducing a time-out effect on some forms, so that they close after a period of inactivity? Taken from this websites TIPs section you could probably amend this procedure...
(First of all you will need to create a macro to execute the Close action on the form.
Now go to the Design View of the Form and open the Properties sheet.
In the TimerInterval property enter the length of time you want the form open for. This should be in milliseconds, so for instance if you want the form open for 8 seconds enter 8000, for an minute enter 60000.)

- Customise the security level so that on logging into the database the key forms are displayed for that user?

As I say - Im new with Access but these are some ideas that spring to mind...
 
I have had problems opening forms for the first time. (taking between 5 and 10 seconds)Some of the reasons are.
i)running application across the network. If you have a limited number of users you could perhaps install local frontends and just have the tables on the network.
ii)Having lots of controls on a form can slow it down, dont record unnecessary data.
iii) having multiple subforms within a form can also slow performance.
You can also run Tools-Analyze-Performance to tweak up your system.
Hope this is of some help and if anyone else has comments I would welcome them as I am still looking to get some improvements out of our system.
 

Users who are viewing this thread

Back
Top Bottom