Tek-Tips is the largest IT community on the Internet today!

Members share and learn making Tek-Tips Forums the best source of peer-reviewed technical information on the Internet!

  • Congratulations Chris Miller on being selected by the Tek-Tips community for having the most helpful posts in the forums last week. Way to Go!

Access Client Side Very Large

Status
Not open for further replies.

trevorwilliams2

Programmer
Mar 3, 2003
107
US
I have an inherited database that I have been re-working.

I split the database into a client server setup. All of my data has been moved to the server side and there is nothing but linked tables on the client now.

The client side is over 100mb, even after compact and repair.

The form and report count is less the 20.

Does not make any sense??????????

It is making extensive use of Tab Controls, not sure if that would make any difference.

Any ideas?
 
Have you run a compact and repair operation on the client side since splitting the database? If not, give that a try. It could end up being all you need to do.

--

"If to err is human, then I must be some kind of human!" -Me
 
I have seen a single corrupted form bloat my db a 100+ megs. So I would do what Duane says. After importing all of your objects, if it does not fix the problem then start over. This time import each form 1 by 1 looking for a possible culprit. If it is not a form, then import each report 1 by 1 looking for a report culprit. You may have to rebuild that form or report.
 
Gave it a try first thing this morning. No dice, still hung up at 111mb.

The import of the objects into a new db went fine until it hit modules. It got to an object I have never seen in a module import. It hung up for about 5 minutes on the object "&Relationships" and then finally finished.

This object is not shown anywhere in the new db.

This is a new one to me...
 
Never heard of that. But how about? Import everything but the modules. Then copy and paste the module text into new modules.
 
Try to Decompile the mdb.
Start --> Run "C:\Program Files\Microsoft Office\OfficeNN\MSACCESS.EXE" "x:\MyMDB.mdb" /decompile

Substitute your folder for OfficeNN (ie Office11, Office12)
 
Do any of your client-side forms have embedded image backgrounds? This can take a lot of space, I believe that MS takes even jpg images and stores them in binary as raw bitmaps, so a 500K jpeg may take 5 megs of space.
--Jim
 
jsteph hit the nail on the head.

This database is newly handed over to me and I hadnt bothered to look through all of the reports in design view yet.

Sure enough...there was a .tiff (why?) embedded in almost all of the reports.

 
That's why I asked "Do you have any images?" on 11/09.

If you need an image or logo, I generally create a small subreport with the image. I then include the subreport on any report that needs the image.

Duane
Hook'D on Access
MS Access MVP
 
Thanks dhookam & jsteph, dumped all of the .tiffs for a subreport (great idea) got it down to 38mb from 112mb.
 
Status
Not open for further replies.

Part and Inventory Search

Sponsor

Back
Top