Corrupt MDW - About Had It :mad:

[SteelersFan]

Background
Multiuser database (10 users concurrently, 120 total). Split db. both on same server. Users access database via a shortcut that has the workgroup file built in. We have had the same the following problem occur probabaly 5 times in the last few weeks.

Problem:

The mdw file keeps getting corrupted with message saying

"Couldn't User [drive]:\Path\File.MDW. File is already in Use"

This is driving me insane and numerous google searches have yielded squat. I did get a response to this earlier that it could be a network problem but this really? This is the answer? My users think Access sux and I'm starting to think that they are right. Access should only be used to store your phone numbers.

Please Help.

Thanks.

 

[ByteMyzer]

This is a network issue.

The users who need to use Access through this workgroup need FULL access to the folder where the database resides, and FULL access to the folder where the workgroup file resides. If they do not, you will encounter the problem you described.

 

[ghudson]

In addition to the fact that the users need full permissions to the network directory that the backend is located on...

Your database must be split. Each user must have a copy of the front end installed onto their PC's hard drive. The Workgroup.mdw file must also be installed onto their PC's hard drive [keep everything together and in the same directory]. All of the front end's [they are the same file just each users PC has a copy] must be linked to the same and only backend file on the network. Eack database file [including the workgroup.mdw] will create a record locking file *.ldb in the same directory that the .mdb and .mdw files are located when the db is opened. The users must have full permissions to those directories so that that can create/edit/delete the record locking .ldb file.

You will have to give each user an updated version of the front end and the workgroup file every time you make design changes to the backend or the front end. There are many ways to automate the file updates and searching this forum will provide you some samples or guidance.

To open the secured db you need to give the users a custom shortcut and the Target field will look something like this [all on one line]...

"C:\Program Files\Microsoft Office\Office11\msaccess.exe" /wrkgrp "C:\Workgroupfile.mdw" "C:\Databasefile.mdb" /user UserName

 

[SteelersFan]

I don't agree.
The front end doesn't need to be on each workstation. That would be a change control nightmare. Neither the mdw file. Both front, back end and mdw file are on a file server. The users use a shortcut that points to the front end and the workgoup file.

"C:\Program Files\Microsoft Office\Office\MSACCESS.EXE" "S:\Share\Database\DB\FrontendDB.mdb" /wrkgrp "S:\Share\Database\DB\MSSecFile.MDW"


This configuration is pretty standard isn't it?

Also, the users have 'change' on the directory. So thats not the problem.

Come on. I thought there were bright people on here

 

[KenHigg]

The Workgroup.mdw file must also be installed onto their PC's hard drive

Sorry, but I have to take exception to this one. Could you elaborate on why you think this is a good idea?


Ken

 

[neileg]

I think it's a network permissions issue as well. You say that users have 'change' on the directory. I don't understand the term. The users don't need full control on the directory, but they certainly need Modify, Read and Write permissions. I've not had any locking or corruption issues arising from having front end, back end and mdw files in the same shared directory. I can't comment on whether this is the best arrangement but it has consistently worked for me.

 

[KenHigg]

Wouldn't that be:

"C:\Program Files\Microsoft Office\Office\MSACCESS.EXE" /wrkgrp "S:\Share\Database\DB\MSSecFile.MDW" "S:\Share\Database\DB\FrontendDB.mdb"

???
Ken

 

[SteelersFan]

They have read/write/delete on the directory that houses the front end, back end and security file. The issue with the mdw file locking/corrupting has happend about 5 times in the last week or two. If it was security, the problem would appear immediately.

Please throw ideas at me. I really need some help on this.

Also, IS it ok to have both front end and back end on the server. We only will have at most about 10 people logging into the database at the same time. More likely, 3-5 people logging in at the same time. The system is to log Atypical Events so its not used by everyone at the same time.


I work in a regulated environement (pharma) and this database is high profile and is being looked at in a bad light because of this.

Any help would be appreciated.

 

[SteelersFan]

Wouldn't that be:

"C:\Program Files\Microsoft Office\Office\MSACCESS.EXE" /wrkgrp "S:\Share\Database\DB\MSSecFile.MDW" "S:\Share\Database\DB\FrontendDB.mdb"

???
Ken

Ken,

Really? I have a custom shortuct creator made by the consultant/company that put the db together.

I cut and pasted it.

Why is what I had wrong?

 

[KenHigg]

It may be the version of access we're using. In my shortcut, you run the exe, then define the wrkgrp then open the mdb.

You know, seems this changed several ver's of access ago...

But if your's works, no prob

Ken

 

[SteelersFan]

Access 97SR2

Would it be futile to call Microsoft directly and ask them about the mdw file corruption problem?

Do they even have tech support?

 

[KenHigg]

I think I would heed the network advice and bump heads with your network people. Maybe going to the extent of recreating a new share folder etc.

MS will most likey be useless...


Ken

 

[SteelersFan]

ahhh the fun of validaiton. Recreating a new folder would cause me to rev my FSDS and also SOPS that point to that folder.

I sent out a mass email telling people to not leave the db up all day. Use it and get out. Also told them to exit by using the exit button and not control+alt+end task or shutting down the pc without closing the app.

Its a big CF right now. Hopefully we can get this to happen only rarely and not everyday.

 

[SteelersFan]

Also, what is a big database? Our back end is 128 mb. Does corruption/problems rise as your db gets bigger?

 

[KenHigg]

Does corruption/problems rise as your db gets bigger?

In my experience, the size problems start to arise because a share/drive/network bandwidth, etc reaches a limit and not so much because Access has a problem. 128m 5-10 user typically shouldn't be a prob, but if everyone is reading/writing the bulk of the 128m at the same time, ie: Most of the data is in one table, then this could cause a performance issue.

Ken

 

[ghudson]

I have never had a record locking problem since I have moved my workgroup.mdw file to the users computer. I have made that suggestion before in other posts and some posters have replied back that it solved their problem.

Think about it...the more files you share, the greater the chance of a problem. That is why you will read from the masses that you should split your db and have the front end installed to each users hard drive and all fronts should be linked to one backend on the server. Why take a chance when it is so easy to split everything and install the user parts onto thier hard drive and link it all to the backend on the server.

I use a custom routine to update everybodies files when ever I post a new version. I am not able to provide samples or code for this but I will list my steps. The front has a version number in a table that is compared with a text file on the network. If the version numbers do not agree, the front end is closed down, a utility db is opened, the utility db copies all of the new files from the network to the users computer, the utility opens the updated front end for the user and then the utility shuts itself down. It is too easy. All I have to do is replace the old files with the new files in a special update directory on the network and change the version number in the text file. But that is my method and my free advice.

SteelersFan:

Come on. I thought there were bright people on here

You get what you pay for. How about them Cowboys!

 

[KenHigg]

I suppose it would work Just never had a need myself, I'll keep it mind though...

Ken

 

[neileg]

Just a thought, you have tried the trivial stuff like a repair and compact?

 

[ghudson]

Just a thought, you have tried the trivial stuff like a repair and compact?

That should be done daily since there are so many users. He will continue to have corruption problems and broken indexes since the front end is shared. It is too easy for one user to trash the front end and the linked data. A locked PC, systems crash, lost network connection, or a Ctrl ALt Delete is all it takes to corrupt it. I have been there, done that, figured out what works and went forward to enjoy life without worrying if a user could hose a db.

 

[Pauldohert]

This is probably really dumb - but how do users get added etc when the mdw has mulitple copies one for each PC?

Paul