Workgroup Information File Missing

[jocat]

I have created an acess database that is to be used by 4 users (including myself). I placed it on the network in a secure folder in which the 4 people have access, thus eliminating the need to use access security, of which I know absolutely nothing. I have done this in the past without a problem (in a different department, on a different computer, in a different secure folder).

My problem is when one of the other users attempts to open the database, he gets the following message "Can't start your application. The workgroup information file is missing or opened exclusively by another user".

No one else has the database opened when this occurs.

The "Default Open Mode" is set to "Shared".

Can anyone tell me how to get this to work?

I am using Access 97 and Windows 98.

Thanks

 

[arrowhouse]

Does anyone have an answer for this one? I have the same issue & very little access knowledge!

 

[jinglin]

Just delete this user and then add him/or her again to the secured folder. This might work!

 

[whloo]

anyone have solution for this? i am having the same problem as well

 

[MoLaker]

Perhaps a little far fetched since jocat indicated (s)he had created the database, but one thing that might cause this is if the user has a desktop icon that was originally set up with a workgroup switch included and that workgroup file is no longer available.

Also, just to make sure, the "secure folder" must have read, write & delete permissions for the logged in users.

After that, jinglin's suggestion might help if you are only having trouble with one specific user.

 

[jocat]

This happened to me back in October. The situation was that I got a new computer at work and they load Access 2000 on all new computers. Since we have a lot of applications still in Access 97, they had to load it also. There were the usual Access 2000 & 97 on the same computer problems that had to be addressed.

It was at that point that I started having the problem. I believe the IT guy identified the missing file and copied it from a disk he had. Since then I had no problem.

If I can flag down the IT guy, I'll ask him exactly what he did.

Jocat