Slow loading form

[santon]

Hello, my problem is I have a form which takes forever to load.
Whole database loads quickly, all forms also, except this one. tried to copy it and then delete some of the controls (access analyzed and said "fewer controls"),
I've tried deleting all the buttons, all macros, I've got to the point where I deleted everything in the form, left only white background, and it is still slow on loading.

Also, I noticed when I open the database, then click on that form, it is the only one that takes too much time to load, but after that slow first load, if you close it (form) and then open again it loads much quicker.
I repeat, that is the only one form that is slow in whole database and I want to know the reason why, so if maybe I can fix something instead of creating everything all over again from scratch.



Also tried exporting that form to another database, didn't help.

[orange]

Perhaps posting a copy of the database with some sample data and instructions for showing the problem form would be helpful.

[Minty]

If you deleted everything and it was still slow then the form probably has a slow running query or huge table as it data source?

[mike60smart]

Try just recreating the Form

[Gicu]

I think you shold check the form's record source and any VBA code in the form's main events (Open\Load\Current).

Cheers,
Vlad

[santon]

Hi, thank you all for your replies.
Form doesn't have any code, query or huge table as record source.
Form's record source is a table, which is record source for two forms (2 different parts of the machine in my factory), but there's barely any records in it.

This is that form. It has macros for new record, saving record etc, it has combo boxes, text boxes, calculated fields, and on the right there are option groups.
They are like some form of mini checklist for the material.

[isladogs]

Try creating a new form and importing the objects a few at a time to see what causes the delay.
My guess is the huge number of radio buttons in the option groups on the right.
You could try putting those in a subform.

You also mentioned that the form is only slow to load the First time. Subsequent reloading is much faster.
As its not your startup form try opening it hidden when you load your startup form (or using a autoexec macro).
Then when you need to use it just open it normally. It should be instantaneous.

[santon]

Try creating a new form and importing the objects a few at a time to see what causes the delay.
My guess is the huge number of radio buttons in the option groups on the right.
You could try putting those in a subform.

You also mentioned that the form is only slow to load the First time. Subsequent reloading is much faster.
As its not your startup form try opening it hidden when you load your startup form (or using a autoexec macro).
Then when you need to use it just open it normally. It should be instantaneous.

I'll try that first part.

About the second part and the autoexec, can you explain a little bit more?
Is this a way to do it? Create a macro, rename it to autoexec, select form and set it to hidden?
Because I've tried this and when I open my database again it is slow because it's loading that slow form

[davegri]

My guess is the huge number of radio buttons in the option groups on the right.

I thought so too, so I created a form to duplicate the radio button layout.

It turns out that the buttons can't be in option groups because Access limits 20 buttons to a group.
Be that as it may, I created the 180 buttons and put boxes around them to appear as shown.
It loads fine and quickly. I added a form open event to iterate thru all the buttons and set them to True. That didn't slow down the load at all.

I suspect that there must be some initialization code running that is gumming up the works.
I'd make a copy of the form and remove all event procedures and embedded macros and control source calculations (one at a time) and see it that loads OK.

[santon]

I suspect that there must be some initialization code running that is gumming up the works.
I'd make a copy of the form and remove all event procedures and embedded macros and control source calculations (one at a time) and see it that loads OK.

I've already tried that. Copying, exporting to another database, didn't help.
There is no code or macro in the form, only macro that was onload to maximize windows, but I've deleted it.
Also deleted all calculated fields from the table and form, still nothing changes

[isladogs]

OK using the autoexec macro to open the problem form hidden was a bad idea.
What you would need to do instead is load a different startup form then use a timer event with a short delay e.g Timer interval =2000 = 2 seconds to load the form as hidden...and then change the interval to 0 to disable the timer.
It may of course prevent use of the visible form in that time period in which case scrap the idea completely.

Thanks to davegri for testing the impact of the 180 radio buttons. Whilst I'm surprised at the result, it might be better to replace all of them with combos with values from 1-30.

Anyway having read your responses, it now looks to be that you have one or more corrupted controls. You need to identify it and then replace it.
I had to do this recently when a Web browser control got corrupted causing a form to hang for up to 30 seconds. After replacing it, the form loaded in a fraction of a second.
My suggestion about importing the objects a few at a time or better still, one at a time, should allow you to deduce which control(s) is/are responsible in your case

[Gicu]

You also mentioned combo boxes, start with those first, look at their row sources as they can slow down loading of the main form.

Cheers,

[santon]

Thank you all for your help, I've deleted the corrupted form and started creating a new one. Got tired of trying to find out what is wrong with the form for the last two days.

New one loads very fast for now

I want to set maximize window setting for my form on load, is it better (faster load) way macro or event procedure?

[isladogs]

Probably almost identical but I would use event procedures as they are more powerful - important if you want to do additional code