Hi all,
In Access2003 I have a frontend of about 2MB (backend is about 1,5 MB and
has about 8 tables). The frontend consists of 4 forms, 6 reports, 2 modules,
and some queries. The biggest and main form in the frontend seems like a
normal form to me. It has a subform in it and in my eyes not too much code.
However, when I make a simple change to the form, for instance making a
field bigger or add a button with 3 lines of code, and I want to save the
form it takes 1 to 2 minutes to save. Although there are no signs of a
corrupt database I tried compact and repair. This action is done properly
but still it doesn't change the amount of time it takes to save the form.
Is this normal behavior? Does anyone has some pointers to further
investigate this?
I'm thinking about rebuilding the whole form but that will take me a lot of
time, escpecially for putting the code in the right places, naming the
fiels, and layouting the form. But if that would be a solution, does anyone
have tips to make this process easier? Maybe a simple copy-and-past action?
Thanks in advance for any advice,
Cheers.
John
Pat Hartman - 25 Jan 2008 20:56 GMT
Here's something to try -
1. Open the form's code module
2. Select all the code and paste it into notepad.
3. Save the file just to be safe.
4. Change the form's HasModule property to no. You will get a warning
message that this will delete all associated code for the form. Say OK.
5. Save the form.
6. Compact the database again.
7. Reopen the database and the form in design view.
8. Paste the saved code back into the form's empty code module.
9. You may have to click on the builder button for each event procedure with
code to "reconnect" the form with the event code since Access doesn't always
recognize code entered this way even if the procedure name is correct.
As with all potentially damaging processes, make a backup before starting.
> Hi all,
>
[quoted text clipped - 22 lines]
> Cheers.
> John
John - 25 Jan 2008 21:04 GMT
Thanks Pat.
I will practice it this weekend and try it out on the dabase on monday.
John
> Here's something to try -
> 1. Open the form's code module
[quoted text clipped - 39 lines]
>> Cheers.
>> John
Albert D. Kallal - 25 Jan 2008 23:51 GMT
This problem is solved nine out of ten times By creating a persistent
connection.
In your case simply open any table in the front that is a linked table have
to the back and look at the data in table. Now, DO NOT CLOSE this table, but
simply minimize this table.
Now try editing and modifying the form or report and you'll find that the
form or report save in an instant.
And, post back here as to how great this works....
The other thing to check is to turn off track name autocorrect....

Signature
Albert D. Kallal (Access MVP)
Edmonton, Alberta Canada
pleaseNOOSpamKallal@msn.com
John - 28 Jan 2008 17:53 GMT
Albert, it works.......great! :-)
John
> This problem is solved nine out of ten times By creating a persistent
> connection.
[quoted text clipped - 9 lines]
>
> The other thing to check is to turn off track name autocorrect....