Re: DB Front End is extremely large !

Tech-Archive recommends: Fix windows errors by optimizing your registry

Try this sequence:

1. Create a new database.

2. Turn off the Name AutoCorrect check boxes under:
Tools | Options | General.

3. Import (File | Get External | Import) the tables, or link them (File |
Get External | Link) if the database is split.

4. Import the other objects (queries, forms, reports, macros, modules.)

5. Set minimal References under Tools | References (from the code window).
If you are not sure what references you need for your version of Access,
see:
http://allenbrowne.com/ser-38.html

6. Compile (Debug menu, from the code window).

7. Compact:
Tools | Database Utilities | Compact

The other thing that can make the front end large is any graphics you have
imported into your forms or reports, or stored in an OLE Object field in a
table.

--
Allen Browne - Microsoft MVP. Perth, Western Australia.
Tips for Access users - http://allenbrowne.com/tips.html
Reply to group, rather than allenbrowne at mvps dot org.

"SodaJim" <SodaJim@xxxxxxxxxxxxxxxxxxxxxxxxx> wrote in message
news:7681F501-02EE-485D-9186-D039A1F2E67F@xxxxxxxxxxxxxxxx

I'm new here and thought this would be the best place to begin fine tuning
my database skills.

I developed an Overtime DB that has worked well for over a year now. I'm
currently working on splitting the DB and have removed almost all the data
in
three tables. I'm leaving data so I can see the results. The problem I've
run
into is that the front end is 14 megs! I only have three tables(BE), four
forms, several querys, and two reports... This DB up until recently was
only
around 3 megs if my memory servers me...

What I have noticed is the Sys Table, MSysAccessObjects, has around 3435
records! I attempted to remove records to no avail.

What's the best avenue to get the FE back to a reasonble size before I
split
the "Live" DB and distibute the FE to the other computers...?

Thanks in advance for any suggestions!

Jim


.

Relevant Pages

  • Re: Reports and Quweeries
    ... Compact the database to get rid of this junk: ... > In my application I have to produce 5 different reports. ... > I created a query for the initial SubReport and the MainReport as well as ...
    (microsoft.public.access.reports)
  • Re: SYSTEMS ENGINEER/ VAX-VMS/ CAREER POSITION
    ... System Administration and database admin from NIIT, ... salary details and generate reports and enclosures,and calculates ... Responsibilities: ... Write New programs from user requirements, Programming Changes ...
    (comp.os.vms)
  • Re: Advice needed for a growing Access 2000 project
    ... However, it turned out that quite a few of those were "leftovers" from previous releases, no longer accessible from anywhere but the database window, and, thus, no longer used. ... But that certainly isn't the _norm_ -- without any 'heroic' measures, there are routine reports of split Access DBs ... Finally, in my opinion, for "Windows apps", that is, individual-user applications, modest-sized multiuser applications, and client-server applications of any size, Dot Net does NOT "help along" any of these issues. ... The post I reference was in reference its self to the MS Access Help file under "Microsoft Access database general specifications" ...
    (comp.databases.ms-access)
  • Re: running report cause fatal error- on Win98, not XP
    ... It is actually not that difficult to crash JET with complex queries, ... another query. ... only the more complex reports cause the crash- the others do ... Then compact the database: ...
    (microsoft.public.access.reports)
  • Re: running report cause fatal error- on Win98, not XP
    ... another query. ... only the more complex reports cause the crash- the others do ... Then compact the database: ... Still in the code window, choose Compile from the Debug menu. ...
    (microsoft.public.access.reports)