MS Access 97 DB Corrupts after Compact

[owengoodhew]

Hi,

I am responsible for maintaining an MS Access 97 Database that reliably
becomes corrupt following a compact.........

About the Database:
The database is made up of three linked databases, data, input and
output. The files all share the same table structures. Recently the
input database started growing in size and it became necessary to
compact the databases more frequently. Following the compact of the
input file the data file will corrupt shortly after.

Question:
When I perform the compact operation should I be compacting all three
components of the database system (data, input and output). My concern
is that when I compact the input file, I am changing the table of the
input file and not making the changes to the data file, which I guess
would cause a corruption.

Also if anyone could give me some ideas to why the input side (User
input forms, queries) of a database system significantly grows in size
this will help in reducing the problems that I am currently
experiencing

Any advice about the correct compacting procedures for a database
structure like the above would be much appreciated. Also if anyone has
any links or information about how the JET engine handles compact
procedures in the linked table situation it would be useful to have a
look at them.

Owen Goodhew

[Br]

ow*********@gmail.com wrote:

Hi,

I am responsible for maintaining an MS Access 97 Database that
reliably becomes corrupt following a compact.........

About the Database:
The database is made up of three linked databases, data, input and
output. The files all share the same table structures. Recently the
input database started growing in size and it became necessary to
compact the databases more frequently. Following the compact of the
input file the data file will corrupt shortly after.
Sounds like it is corrupted to start with. I'd recreate the input file.
Create a new db and import the tables/etc.
Question:
When I perform the compact operation should I be compacting all three
components of the database system (data, input and output). My
concern is that when I compact the input file, I am changing the
table of the input file and not making the changes to the data file,
which I guess would cause a corruption.

No, shouldn't be a problem.
Also if anyone could give me some ideas to why the input side (User
input forms, queries) of a database system significantly grows in size
this will help in reducing the problems that I am currently
experiencing
I assume you are inputting data and then processing it, then perhaps
deleting the input data? Access grabs "chunks" of space when needed and
does not release it when objects are removed (until you do a compact).
Any advice about the correct compacting procedures for a database
structure like the above would be much appreciated. Also if anyone
has any links or information about how the JET engine handles compact
procedures in the linked table situation it would be useful to have a
look at them.

I don't think it makes any difference (expect if you are talking about
if the file is in use). You should compact all you data files as a
regular general maintenance.
--
regards,

Bradley

A Christian Response
http://www.pastornet.net.au/response

[MacDermott]

You say the 3 databases (MDB files?) share the same "table structure".
Does this mean that the data is distributed across all 3 MDBs?
Or are all the tables in the "data file", with the input and output files
linking to it?

<ow*********@gmail.com> wrote in message
news:11**********************@g14g2000cwa.googlegr oups.com...

Hi,

I am responsible for maintaining an MS Access 97 Database that reliably
becomes corrupt following a compact.........

About the Database:
The database is made up of three linked databases, data, input and
output. The files all share the same table structures. Recently the
input database started growing in size and it became necessary to
compact the databases more frequently. Following the compact of the
input file the data file will corrupt shortly after.

Question:
When I perform the compact operation should I be compacting all three
components of the database system (data, input and output). My concern
is that when I compact the input file, I am changing the table of the
input file and not making the changes to the data file, which I guess
would cause a corruption.

Also if anyone could give me some ideas to why the input side (User
input forms, queries) of a database system significantly grows in size
this will help in reducing the problems that I am currently
experiencing

Any advice about the correct compacting procedures for a database
structure like the above would be much appreciated. Also if anyone has
any links or information about how the JET engine handles compact
procedures in the linked table situation it would be useful to have a
look at them.

Owen Goodhew

[owengoodhew]

Hi,

Thanks for your response......

The data mdb is the main file. The input and output mdb files are
linked to the data file. The input/output mdb files have been used so
that the data and forms/tables/queries are kept seperate.

Regards,

Owen Goodhew

[owengoodhew]

Hi,

Thanks for your response......

The data mdb is the main file. The input and output mdb files are
linked to the data file. The input/output mdb files have been used so
that the data and forms/tables/queries are kept seperate.

Regards,

Owen Goodhew

[MacDermott]

Isn't the data in tables?
(You said it was separate from the "forms/tables/queries")

<ow*********@gmail.com> wrote in message
news:11*********************@g43g2000cwa.googlegro ups.com...

Hi,

Thanks for your response......

The data mdb is the main file. The input and output mdb files are
linked to the data file. The input/output mdb files have been used so
that the data and forms/tables/queries are kept seperate.

Regards,

Owen Goodhew

[Br]

ow*********@gmail.com wrote:

Hi,

Thanks for your response......

The data mdb is the main file. The input and output mdb files are
linked to the data file. The input/output mdb files have been used so
that the data and forms/tables/queries are kept seperate.

Regards,

Owen Goodhew

Sounds confusing...

Perhaps give us an example of the objects and their use in each MDB
file....?
--
regards,

Bradley

A Christian Response
http://www.pastornet.net.au/response