G
Guest
Here's what's going on:
We receive a flat file from a customer and import it into Access. once the
file is in Access, we have scripts that copy it from Access into Oracle
(EDon't ask me why we do it this way, i just work here).
We received the files last montha nd placed them in a access db that we
names hwes021606.mdb. It is 77,600 bytes big.
This month we go through the asame process and produce a mdb file that is
named hwes032206.mdb and is 52,876 bytes long.
Little or no activity has impacted the database since last month.
My question is this: Should i be worried about the disparity of the the
datbase physical size?
We receive a flat file from a customer and import it into Access. once the
file is in Access, we have scripts that copy it from Access into Oracle
(EDon't ask me why we do it this way, i just work here).
We received the files last montha nd placed them in a access db that we
names hwes021606.mdb. It is 77,600 bytes big.
This month we go through the asame process and produce a mdb file that is
named hwes032206.mdb and is 52,876 bytes long.
Little or no activity has impacted the database since last month.
My question is this: Should i be worried about the disparity of the the
datbase physical size?