Forms Slow to Save and go into Design View

[iheartvba]

Hi,
This is driving me absolutley insane! Every time I want to take a very complex from into design view or save it after amending it in design view, it takes ages to save. All I can think of is that I make all my queries in the Form e.g. if I have a list box I will have saved the query in the row source of the list box instead using VBA listbox.rowsour ce = "query". What would be the best way to make the forms faster (to go into and come out of design view)???

Please help... before I go bald pulling my hair out...

Some forms just Crash when I save from Design View... "Catastroph ic Failure" it says, Catastrophic, I never knew Access had such depth of emotion, but it seems I have made it panicked and afraid, I don't think it will stay on my computer after many more catastrophies.

[JustJim]

Hi,
This is driving me absolutley insane! Every time I want to take a very complex from into design view or save it after amending it in design view, it takes ages to save. All I can think of is that I make all my queries in the Form e.g. if I have a list box I will have saved the query in the row source of the list box instead using VBA listbox.rowsour ce = "query". What would be the best way to make the forms faster (to go into and come out of design view)???

Please help... before I go bald pulling my hair out...

Some forms just Crash when I save from Design View... "Catastroph ic Failure" it says, Catastrophic, I never knew Access had such depth of emotion, but it seems I have made it panicked and afraid, I don't think it will stay on my computer after many more catastrophies.

Have you tried Compact and Repair?
Also, try not clicking too loudly, you might be scaring the poor little beastie!

Jim

[iheartvba]

yes, many many a time have I gone down the route of compact and repair, I have, but it seems like it Access has been violated too many times it has suffered too many catastrophies, anarchies, wars, famines, pain and suffering then it could bare, I am now just going to revamp the forms and feed them SQL via VBA instead of putting them on the forms, it does make the forms faster, but it takes a long time to revamp the form. My advice: Always Always Always, feed your forms queries from Vba don't save it permanently in the row sources if possible.

[JustJim]

My advice: Always Always Always, feed your forms queries from Vba don't save it permanently in the row sources if possible.

I'm hearin' ya.

Jim

[NeoPa]

It's not impossible (or even unlikely at a guess) that your database has some corrupted elements in it. Not everything is fixed by a Compact & Repair (unfortunately) .

Consider creating a new database from scratch and importing objects into it from this one.

Be careful and test before any objects you have any suspicions of.

It may turn out to be that individual form alone, but I doubt it can hurt to try it out.

Good luck.

[FishVal]

... My advice: Always Always Always, feed your forms queries from Vba don't save it permanently in the row sources if possible.

To the best of my knowledge RowSource property is nothing more than a string property containing SQL expression. There is nothing resource consuming or unsafe in using them.

"Catastroph ic failure". :D
I was impressed too when saw it first time.
As far as I could recall this error occurs when Access fails to communicate with Activex OLE server. Do you have Activex control(s) on your form?

Regards,
Fish.

[iheartvba]

Hi,
I have just gone on another persons laptop today (which was about as powerfull as my PC) and the the Reports and Forms on his laptop loaded about 10 times as fast as on my PC. We both have MS Access 07. Why would this be, when I go into design view my access takes ages.

[mshmyob]

Hi,
I have just gone on another persons laptop today (which was about as powerfull as my PC) and the the Reports and Forms on his laptop loaded about 10 times as fast as on my PC. We both have MS Access 07. Why would this be, when I go into design view my access takes ages.

I use Access 2007 also and have run across this problem also. I have forms with embedded rowsource queries and also forms that link to queries for rowsource. It does not appear to be the cause though.

I find it slows down after a marathon session of programming from switching back and forth from design mode to form view it slows down. It appears to me that Access keeps allocating memory when going in and out of design mode and form view and doesn't seem to release it properly. It therefore slows right down after numerous switches.

I have been able to fix the problem by cloing access and reopening or rebooting. Keep in mind this happens rarely and after many design/form view switches (sometimes hours).

I don't know if you have the same scenario.

cheers,

[ChipR]

I often get crashes when switching from design to form view and back, especially on forms with subforms, so I've taken to just closing the form and then re-opeing it in the other view every time. It's kind of a pain, but it's quicker than restarting Access all the time, and I haven't seen any slowing.

[mshmyob]

I often get crashes when switching from design to form view and back, especially on forms with subforms, so I've taken to just closing the form and then re-opeing it in the other view every time. It's kind of a pain, but it's quicker than restarting Access all the time, and I haven't seen any slowing.

I have never had AC2007 crash on me (fingers crossed). Just the slow down like I mentioned. But it does sound like there seems to be a problem with switching between design/form view since your problem is also associated with that sequence of events.

cheers,

[iheartvba]

I have just seen an improvement in the speed recently after an update was done to MS Office, still abit slow, but I can live with it.

[Megalog]

I had the same problem, on some very complex forms. It was usually a matter of rebuilding the form from scratch that would solve it (some kind of form-bound corruption). In some other cases, I had to rebuild the entire database by re-importing all the objects into a new one..

The one common ground I had on all of these problem databases, is the format was originally 2003/mdb, upgraded to 2007/accdb. After re-importing everything into a blank ACCDB, they tend to behave for a while.

On another note, I'm beta testing office 2010. I loaded up one of my bigger databases, did a compact/repair, and it permanently removed 20MB off the size. Normally it would get to be about 70mb after a few hours in design.. I would compact/repair and it would drop to 40mb. After the Office 2010 compact/repair, it would go down to 20MB! The database still works just fine using 2007, so maybe there's some extra junk that 2007 stores in the 'Msys' tables that isnt getting properly cleared out.

[iheartvba]

Thanks Megalog,
Just wondering is there a smart way to import forms etc into a new accdb file or should I just do a copy and paste?

[NeoPa]

The Import process can handle multiple objects, including not just Tables, but also Forms, Reports, Queries, etc.

[iheartvba]

Hi NeoPa the Import process worked brilliantly. The DB is working much better now. The only thing I would like to know is how can I regularly maintain the database so it doesn't get to the stage where I need to import the Items into a new database shell.

Thanks