Database Bloat Problems

[Scott Duncan]

Hello,

We are using MS Access 2003 on XP Pro Machines.
Database is split into Front End & Data [Back End]

During [normal minor] Front End Development the size of the Database bloated
to almost double it's original size.

Went thru and Compacted & Repaired. Made very little difference.

Then decompiled using:
"C:\Program Files\Microsoft Office\OFFICE11\msaccess.exe" /decompile "c:\My
Documents\FrontEnd.mdb"

Then, Compacted & Repaired again and still nowhere near the original size.

Created a new database 'NewFrontEnd.mdb" as a blank Database.

Started by linking all of the tables that are required.

Then, Imported the Queries from FrontEnd.mdb. Took a very long time and
Access finally failed.
Tried it again on another Machine [all are XP Pro] with the same result.

Compacted what I had so far and started importing the Forms, Reports,
Modules and Macros.

Each time it took an inordinate amount of time.

With Access 2000 and Access XP, this process that relatively quick and
painless...

Is there something that I am overlooking ???

Any suggestions would be greatly appreciated.

TIA,

SD

 

[Guest]

It would be interesting to know what sort developments you were doing at the
time. I had a client with a very similar question a while ago, and it turned
out he had added some nice graphics to some of his forms and reports,
althought the grpahics were small as a.jpg, when they were imported into the
database a few times (He embedded the picture in each report / form rather
than linking to them) the database bloated massively. Could this be your
problem?

Neil
www.nwarwick.co.uk

 

[Scott Duncan]

Neil,

Thanks for the reply...

The modifications that we were doing did not affect any graphics as you
suggested. We have seen an OLE Error from time to time that related to
linked graphics.

I can not seem to put my finger on this problem.

Moreover, I do not know why it is so difficult to create a new, blank
database and import all of the Queries, forms, ect... It very quick &
effective with Access XP.

Thank you again,

SD

It would be interesting to know what sort developments you were doing at
the
time. I had a client with a very similar question a while ago, and it
turned
out he had added some nice graphics to some of his forms and reports,
althought the grpahics were small as a.jpg, when they were imported into
the
database a few times (He embedded the picture in each report / form rather
than linking to them) the database bloated massively. Could this be your
problem?

Neil
www.nwarwick.co.uk

Hello,

We are using MS Access 2003 on XP Pro Machines.
Database is split into Front End & Data [Back End]

During [normal minor] Front End Development the size of the Database
bloated
to almost double it's original size.

Went thru and Compacted & Repaired. Made very little difference.

Then decompiled using:
"C:\Program Files\Microsoft Office\OFFICE11\msaccess.exe" /decompile
"c:\My
Documents\FrontEnd.mdb"

Then, Compacted & Repaired again and still nowhere near the original
size.

Created a new database 'NewFrontEnd.mdb" as a blank Database.

Started by linking all of the tables that are required.

Then, Imported the Queries from FrontEnd.mdb. Took a very long time and
Access finally failed.
Tried it again on another Machine [all are XP Pro] with the same result.

Compacted what I had so far and started importing the Forms, Reports,
Modules and Macros.

Each time it took an inordinate amount of time.

With Access 2000 and Access XP, this process that relatively quick and
painless...

Is there something that I am overlooking ???

Any suggestions would be greatly appreciated.

TIA,

SD