Access split database

[Polarbear]

This may have already been answered but I couldn't find anything specific on
the site. I am working with a split database where I recently backed up the
FE which was 29,000 KB. I updated a table in the BE, linked it to the FE and
then went to copy to my backup. I noticed that the FE was only 7,000 KB and
the FE backup was 29,000 KB. Does anyone know why the backup is larger than
the FE? I'm not sure if I messed something up or not. This is a shared
database and I've only started working on it.

Previous saved versions of the backup (by other people) were 8,000 KB and
14,000KB.

Thanks,

 

[Jeff Boyce]

The risk you run with using Compact on Close is that "oops happens",
sometimes in the middle of the compact, totally munging your database. The
risk of a user turning off his/her PC, or a power-surge, or a network
hiccup, or .... may be enough to decide not to allow Access to automatically
Compact on Close, but rather, to make a backup copy periodically and
"manually" running Compact.

JOPO (just one person's opinion)

Regards

Jeff Boyce
Microsoft Office/Access MVP

 

[Polarbear]

Thanks very much for your quick response. It sounds like this is the problem.

--
DL

I did not - and have never - told anyone to use compact on close.

Chris
Microsoft MVP

The risk you run with using Compact on Close is that "oops happens",
sometimes in the middle of the compact, totally munging your database. The
risk of a user turning off his/her PC, or a power-surge, or a network
hiccup, or .... may be enough to decide not to allow Access to automatically
Compact on Close, but rather, to make a backup copy periodically and
"manually" running Compact.

JOPO (just one person's opinion)

Regards

Jeff Boyce
Microsoft Office/Access MVP

If you compacted the FE after you backed it up, the compacted FE is
usually

[quoted text clipped - 22 lines]

Thanks,

 

[Polarbear]

Thanks very much for your quick response. It sounds like this is the problem.

--
DL

The risk you run with using Compact on Close is that "oops happens",
sometimes in the middle of the compact, totally munging your database. The
risk of a user turning off his/her PC, or a power-surge, or a network
hiccup, or .... may be enough to decide not to allow Access to automatically
Compact on Close, but rather, to make a backup copy periodically and
"manually" running Compact.

JOPO (just one person's opinion)

Regards

Jeff Boyce
Microsoft Office/Access MVP

 

[Jeff Boyce]

My bad. Your previous post ask if the poster had compact on close turned
on. Without the additional advice "don't!", it could be interpreted as a
suggestion to do so.

Jeff B.

I did not - and have never - told anyone to use compact on close.

Chris
Microsoft MVP

The risk you run with using Compact on Close is that "oops happens",
sometimes in the middle of the compact, totally munging your database.
The
risk of a user turning off his/her PC, or a power-surge, or a network
hiccup, or .... may be enough to decide not to allow Access to
automatically
Compact on Close, but rather, to make a backup copy periodically and
"manually" running Compact.

JOPO (just one person's opinion)

Regards

Jeff Boyce
Microsoft Office/Access MVP

If you compacted the FE after you backed it up, the compacted FE is
usually

[quoted text clipped - 22 lines]

Thanks,