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 TouchToneTommy on being selected by the Tek-Tips community for having the most helpful posts in the forums last week. Way to Go!

Compacting database beyond Compact & Repair command 2

Status
Not open for further replies.

lmn

Programmer
Apr 3, 2003
60
US
Hello,
I sometimes like to take my work home with me and send the MDB file to my home account via email. Now the database is 15MB and it zips to almost 4 MB which is too large for my mail programs to accept.

Is there a better way to compress the database even further?
My biggest table has about 6000 rows x 60 columns. It isn't really a huge database at all (or shouldn't be).

Any ideas?

 
Hi,
It sounds like you have a single database, correct? Well, you should have two database files for security purposes. The front-end database will contain the forms, queries, reports, modules, etc. The back-end database will have all the tables, or at least most of them. With two databases, it is much easier to copy them to separate floppies. Of course, one of the other options is to get a Zip Disk with at least 100MB capacity.

HTH, [pc2]
Randy Smith
California Teachers Association
 
Actually it's all one database right now.

This place is a bit archaic in their techology.

I have the database on my computer and I enter all new information (or pull in info from a different data source where I have to do it via Excel - the system is old and they don't set up data feeds to tables).

I have no strategy at the moment in getting this thing online. Some people have heard the buzz about this database and now want to use it - but there is no central server based place where tables are stored (and can be updated centrally so that no one risks the chance of overwriting someone else's updates).

I have not determined how to do the synchronization stuff - another dilemma - and whether or not I can convince the IT organization here to build me a few tables in a SQL database somewhere...

It has all the makings of a true disaster :)

In a nutshell - all that long response from me to say I have one database and no plans at this time to convert it to two... :-/
 
HI,

You can try decompiling the database. It always makes a HUGE difference in the size of the databases I support. Try this link and see what happens. I think you will be happy with the results.


Have A Great Day!!!, [bigglasses]

Nathan
Senior Test Lead
 
You have chosen to recognize nathan1967 for a helpful or expert post! Thanks for letting nathan1967 know their post was helpful.


And well deserved Nathan. Thats my 'one valuable thing' I've learnt today - I can go home happy now!





G LS
accessaceNOJUNK@valleyalley.co.uk
Remove the NOJUNK to use.
 
Thanks for the response - tho I don't think it's doing me much good.

I get the following message:
The command line you used to start Microsoft Access contains an option that Microsoft Access doesn't recognize. Exit and restart Microsoft Access using valid command-line options.

If I hit ok - it does open access and looks like it wanted to compress it. So I exited, and then hit shift (to halt the autoexec) - then went in and did a compact/repair and it did nothing for the size. The 17MB database file is still1 17MB. I compact/repair on a regular basis - and it has definitely taken a 26MB to a 17MB and I was hoping this would make it even smaller.

Am I doing something wrong?

My command line is as follows:

"C:\Program Files\Microsoft Office\Office\MSACCESS.EXE" "c:\lisa\databases\gc database_new.mdb" /decompile'
 
I think your problem might be the single qiuote make at the end of the /decompile - that you've accidentally copied from the original string in the earlier post.




G LS
accessaceNOJUNK@valleyalley.co.uk
Remove the NOJUNK to use.
 

First, thanks for the star, LittleSmudge. The website has a lot of good information on compacting and speeding up an Access database.

Second, lmn, I agree that the single quote is probably your culprit. The database should start up with no problems and no error messages. Once started, dont forget to go to the VB Editor window (use Alt-F11), choose Debug from the toolbar, and compile. After its finished, close the vb editor and run the Compact/Repair utility. You should see a big difference in file size.

HTH

Have A Great Day!!!, [bigglasses]

Nathan
Senior Test Lead
 
I must be doing something wrong cause it won't budge from 17 MB.

It's not a huge deal and I really don't want to invest much more time playing with it - but for what it's worth - this is what I'm doing...

Ran the command the directions said to so (I took out the ')

It then opens my database. If I have SHIFT down when I run the decompiler - it bypasses the autoexec file and just opens the database.

I then hit Alt-F11 from my main screen and selected debug, et al...it did nothing. There was a status bar that went across the top - quickly I may add - almost as if it only compiled one thing - but it didn't change the size.....

Need to spend time putting out other fires tho so this one will have to simmer on the backburner for a while... :-/

Thanks for your help
 
You have chosen to recognize nathan1967 for a helpful or expert post! Thanks for letting nathan1967 know their post was helpful.

Another one from me. Also, the link on that page back to the ACCESS page there has a whole lot of interesting links to specialized code. Mark that page as favorites also to everyone.

Kudo's Nathan

Bob Scriver
 
Is the problem the fact that I don't have VB on my desktop?????
 
Status
Not open for further replies.

Part and Inventory Search

Sponsor

Back
Top