- first make a backup copy of the database jus tin case something goes wrong.
- If you have code associated with the problem form copy all of it into a NotePad text file and save it.
- While in that form's design view find the Property "Has Module". Change it to No and save the form.
- Compact the database.
- Open the form and change the Has Module property back to Yes. Open the code page and paste in the code from the text file you made earlier.
- Save the form.
- Compact the database again.
---In MS_Access_Professionals@yahoogroups.com, <firstname.lastname@example.org> wrote :
I am working on a new database. It is a linked database and is relatively small: 10 tables, 10 forms, a few reports. All of a sudden the db 'ballooned' from approx 10 MB to 112 MB, I ran a compact and repair and it went down to 42MB. I then imported all objects to a new database. but the new database is even larger:130MB.
After I compacted and repaired, i also made a new MDE. The old MDE was 3.2 MB, the new one is 38MB.
This happend as I was in middle of working on a form: redefining the child/master definition on a subform to a form. the 'wheel' starting spinning for a very long time and the database inflated.
I went back to a saved copy , and redefined the the child/master definition. I compacted the DB and it is now 5MB.
What did I do? What happended? I am looking to avoid this in the future.
Posted by: email@example.com
|Reply via web post||•||Reply to sender||•||Reply to group||•||Start a New Topic||•||Messages in this topic (2)|