database size Farm workers 115 meg and little info

A

Annelie

I used an existing database, deleted most unused items, created my own
tables for my farm workers time card program and calculations of the hours
worked and payment due them. I update this into a year to date table which
started in January of this year. I used the old database mainly to able to
re-use existing form and reports.
It works fine, be while the original database that I copied from has about
25 meg but is holding much more data and horrendous number queries and
reports and queries, it also stores data per jobs, per Employees, per
account no, going back to November of 2002. This database is split front
and back end. I am doing an incredible amount of calculations in there. We
import 4 tables from access to the able to do job costing, billing, payroll
reports, and combination of both.

So here I am with this rinky dinky little database which shows 115 megs and
there is not much information in it. I recreated this database by manually
inputting figures from my spreadsheets starting with January 1, 2004,
manually re-inputting the date and time and updated each week to a Year to
date Table.It was a great test, with only 3 contract workers only. I used
the example on Allen Browne's website on how total calculate time and it
works.

Are those time calculation taking up all this room? When I update each week
to a year to date table, it drops data into that table, not calculations. So
why does this database continue to stay to big??.

The punch in time and punch out time from the time card, I am unitizing
converting hours to minutes and back.
What could be causing for this database to get to big, when I enter only 3
line? Until 3 weeks ago, we on had 3 permanent employees and keeps track of
the earning from the timecard and now we are adding farm piece workers. I am
literally using only 6 tables. and 4 queries for the database. Each week
then get updated to the year to date table with the results for the week
with append queries, but that date goes there already calculated, jut to be
able to pull year to date reports, which I have not even written.

When I copies the existing database for me to use for my own business used
only 25 meg between front end and back end.
What is going on?
Help Annelie
After compact and repair there is no change.
How do I get the size down. Compact and report does not do it.
Annelie
Thank heaven for spell-check
 
R

Roy Goldhammer

Fisrt Of all Annelie

If you want to get answers about your questions just ask the question you
want without telling the hole story

It seems like you don't compact your own database. When you delete table or
data on it Access file size is being increased. This whay you should compact
it for time to time

Secondly it seems that you carry two mutch data on your access database

There are 3 normalization rules about designing the database. It seems that
you haven't use them.

I reach to 100,000 rows and the biggest database i had so far was 10Mb

Check these rules.

Good luck
 
A

Annelie

But I did compact and repair several times over and over. I have finally
decides to just create a new database and at the same time split it. Just
completed the data portion and turned out to be not even 2 megs. When I
imported the front end, the forms took forever, and sure enough, the
database grew to be 500 some odd megs, and after compacting to 335 megs.
When I tried to open the switchboard in the new front end it took forever to
open. I deleted the switchboard and after compacting the new front end is a
little over on meg.
I don't understand what could have happened. The switchboard was not big, my
switchboard items table has only 37 lines. But it sure looks like I need to
recreate it from scratch.
Does anyone have any idea, what could have gone wrong with the switchboard?
Annelie
 
A

Annelie

I found the answer. I put our logo 3x on the switchboard. They are jpeg
pictures, each was 227 kb before I put them on the switchboard.
But, after I deleted all of them, I re-imported the switchboard again and
after compacting, the front end is now just 1.2 megs in size.
Also my original 115 meg file is now down to 5 megs. What in the world did
access do with these pictures?
Annelie
 
T

Tony Toews

Annelie said:
I found the answer. I put our logo 3x on the switchboard. They are jpeg
pictures, each was 227 kb before I put them on the switchboard.
But, after I deleted all of them, I re-imported the switchboard again and
after compacting, the front end is now just 1.2 megs in size.
Also my original 115 meg file is now down to 5 megs. What in the world did
access do with these pictures?

I was just going to suggest that might be your problem. Yes, Access
converts jpgs to bmps and saves thumbnails bloating the database
horribly. Your example is rather extreme though even for Access but
a 227 kb jpg is a bit larger than usual for what I've seen.

You don't want to embed graphics into a table as this causes
significantly bloating of the database. Frequently about one Mb per
graphic.

For more info see the Image Handling Tips page at my website.
http:\\www.granite.ab.ca\access\imagehandling.htm

Tony
--
Tony Toews, Microsoft Access MVP
Please respond only in the newsgroups so that others can
read the entire thread of messages.
Microsoft Access Links, Hints, Tips & Accounting Systems at
http://www.granite.ab.ca/accsmstr.htm
 

Ask a Question

Want to reply to this thread or ask your own question?

You'll need to choose a username for the site, which only take a couple of moments. After that, you can post your question and our members will help you out.

Ask a Question

Top