Access Database Creates New Workgroup File

[iheartvba]

Hi,
I have got a workgroup file which is not in the default Ms Office folder, so sometimes if the computer is restarted after a power surge etc. Access creates a new workgroup file in the default Ms Office Folder. How do I stop this from happening I want the database to always be associated to the Workgroup file that I have specified.

Thanks

[NeoPa]

I'm not sure how to explain this. If you have a situation where the system loses it's pointer to the workgroup file (not one I've come across before btw) then, unfortunately, it won't know about the correct workgroup file (obviously). Getting this to detect the problem and fix it is a bit like a teacher asking everyone in the class for a show of hands of all those absent today.
You can create a task that will do the fix (set up a registry update file to apply) but triggering it to run when the system is broken is another matter entirely.

[Jim Doherty]

Hi,
I have got a workgroup file which is not in the default Ms Office folder, so sometimes if the computer is restarted after a power surge etc. Access creates a new workgroup file in the default Ms Office Folder. How do I stop this from happening I want the database to always be associated to the Workgroup file that I have specified.

Thanks

rather confused...if you are implementing access's integral security mechanism and I'm assuming you must be? given that you seem to be targetting a workgroup file in a disk location other than the retail runtime default installation location, then the alternative location should be referenced in a command line argument switch to keep the database in synch with the alternative wrkgroup file anyway ir am I off track with what you mean.

Have a look at this MS website link dealing with command line switches and see if it is helpful to you (the relevant section for you being in the penultimate command section of the command line switch list)

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

Regards

Jim :)

[iheartvba]

rather confused...if you are implementing access's integral security mechanism and I'm assuming you must be? given that you seem to be targetting a workgroup file in a disk location other than the retail runtime default installation location, then the alternative location should be referenced in a command line argument switch to keep the database in synch with the alternative wrkgroup file anyway ir am I off track with what you mean.

Have a look at this MS website link dealing with command line switches and see if it is helpful to you (the relevant section for you being in the penultimate command section of the command line switch list)

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

Regards

Jim :)

Thanks Jim,

I'm a bit daunted by the command line idea because i really don't understand it. what is happening is that there are a few people on a peer-to-peer network accessing the same database, so that is why I have just put the mdw file in a location on one workstation and linked all access front ends to that file, would it be a solution to just have an mdw file on each persons computer and link their front end to that particular file, basically what I'm trying to first figure out is this, is it possible that this problem is occurring because I have not kept the security file in the default folder location with the default file name.