Compact and Repair Issue on Network Drive

[graviz]

I have a database located on a network drive that I would like to compact on close. I know how to do that, however when it does this on the network drive it renames it to db1. Is there a way to do this and maintain the name of the database?

 

[pbaldy]

In a network environment, an application should be split. The back end containing data would stay on the network, the front end with everything else should be on the user's PC. The db1 file is actually a normal part of a compact/repair, which is normally deleted. The fact that it's not means something is going wrong with the C/R (which shouldn't generally be done over a network anyway.

 

[graviz]

For what I'm trying to do, I can't have part on the network and part on my desktop (at least I think I can't). I have a database that I setup as an autojob so it runs daily. I used to have the database on my local drive, however when I was gone and it failed I couldn't have anyone on my team run it. Now with my databases I store them on the network drive so if my desktop fails someone else on my team can run it from their computer via the network. All my other databases are fairly small except for this one so I don't need to compress the rest of them. Does this make sense?

 

[pbaldy]

I don't see how it matters. The other people on your team could also have a copy of the front end on their PC. That db1 file is telling you Access is having trouble compacting over the network.