Does the Repair in Access 2007 work right? 1

[ToyFox]

My Access 2007 databases continue to grow in size. If I delete old tables and do a repair the filesize remains the same...If I repair it in 2003 the size is reduced.
Can someone explain if this is a bug and will SP2 fix it?

Thanks

 

[kjv1611]

I've repaired several Access 2007 database with not one problem like you're mentioning.

Were the tables you deleted empty?

Also, that would make me wonder whether Access is automatically resizing itself upon deletion of said tables. Perhaps you can try deleting some large tables in a database (of course, use a fake database or either a copy of an existing database), and check the file size before/after each deletion to see if it's changing.

--

"If to err is human, then I must be some kind of human!" -Me

 

[ToyFox]

That's exactly what I did. The 2007 databases that I support are growing in size. The 2007 repair does not change the filesize at all. Its very puzzling.

 

[jrbarnett]

Did you do a compact as well as a repair?

John

 

[kjv1611]

I didn't know you could do one without the other. Is there a way to do so? I'd like to know, just out of curiosity.

--

"If to err is human, then I must be some kind of human!" -Me

 

[jrbarnett]

Look in Access help for a document titled: "Help prevent and correct database file problems by using Compact and Repair"

which covers the compact option.

Change the end parameter to:

/repair

to just do a repair.

Under earlier versions there was an undocumented /decompile option which would remove the "compiled" VBA code and was very useful in sorting out problems with code misbehaving. I haven't had a chance to test this with 2007 to see if this is still available.

John

 

[kjv1611]

Thanks for the info, John.

--

"If to err is human, then I must be some kind of human!" -Me

 

[ToyFox]

OK I figured it out. I copied one of the databases to my C: drive and compacted it there and it worked, when I compact it on the network drive it does not change.
Must be permissions....does anyone know what I need to change. Thanks

 

[lameid]

ToyFox,

Once you compact it locally, copy it back to the network and see if the network reports a smaller size than the original. Replacing the original should indicate any Filesystem security issues.

I'm still using 2003 myself.

Perhaps it does not do the compact over the network for some reason? That doesn't make sense but just throwing out ideas.

 

[ToyFox]

The network reported the same size as the local "C" drive,
also I have now heard that other people have had the same issue. I am not clear what you mean by..."replacing the original should indicate any Filesystem security issues.
I overwrote the network version with the repaired version from the local "C" drive.

 

[lameid]

If it was a network security problem you would not be able to overwrite the network file.

If you open the file on the network, and push ctrl+G to get a VBA windo and in the immediate pane type the following and press enter, does the path begin with a mapped network drive or is it a UNC (\\Servername\sharename) ?

? Currentproject.path

If it is a UNC path, for grins try mapping a network drive and opening it via the mapped drive and do the compact repair and also run the code aboce to see if something different appears.

 

[ToyFox]

It begins with a mapped newtwork drive.

 

[lameid]

The only references I found are for using offline folders which was referenced as bad. I haven't used offline folders but I expect that the client machine could end up with a later version and later overwrite the network copy. I'm not sure how this fits in. The few times I see threads for this issue, the threads die without resolution