Question Compact & Repair Problem

[ScorcherFilms]

In my previous experience, Compact & Repair creates a temporary file, DB1.mdb, etc, to perform the C&R. This then gets renamed to the original filename and the old file gets deleted when the C&R completes.

What's happening at the moment is that this renaming and deleting is not being done. The original mdb is left intact and is reloaded; the new temp DB1.mdb is left in the same folder and is actually the freshly C&R'ed file.

Can anyone tell me why this is happening and what the fix is, please?

I'm using standard C&R (from the menu) in Access2003/SP3 on WinXP Pro/SP3.

Cheers

Martin

 

[DCrake]

This is usually the case if there is a problem when Access tries to compile the mdb. Go into any module and select Debug > Compile before you run the C & R.

David

 

[ScorcherFilms]

Thanks for prompt response, David!

Tried what you suggested but it still left the files as per my original message.

Thing is, I've been using Access for years with no trouble, yet this problem has only emerged recently.

Any other thoughts, please?


Cheers

Martin

 

[DCrake]

Try creating a blank database and import all the objects in to it except the tables.
Then use the link tables manager to link the back end to the front end.

Then Run a C & R.

See if that cures the problem

David

 

[ScorcherFilms]

Hi David, thanks!

I already had a front-end/back-end structure and was getting the problem with both ends.

I took your advice and re-imported to brand new files, which is also a solution I've used in the past to fix corruptions. Sadly, this time, it still hasn't fixed the problem.

Any other thoughts, please?

Cheers

Martin

 

[WIS]

In my previous experience, Compact & Repair creates a temporary file, DB1.mdb, etc, to perform the C&R. This then gets renamed to the original filename and the old file gets deleted when the C&R completes.

What's happening at the moment is that this renaming and deleting is not being done. The original mdb is left intact and is reloaded; the new temp DB1.mdb is left in the same folder and is actually the freshly C&R'ed file.

Can anyone tell me why this is happening and what the fix is, please?

I'm using standard C&R (from the menu) in Access2003/SP3 on WinXP Pro/SP3.

Cheers

Martin

This is a known problem with A2003 SP3 - see this site:

Access 2003 SP3 hotfix site

http://support.microsoft.com/kb/945674

 

[ScorcherFilms]

Many thanks, WIS,

The MS remedy will probably fix it. However, I now have to follow software download approval procedures. (

Cheers

Martin