Lock File Need Help

[AccessHawaii]

I posted a message in here about a week ago about having problems with Novell and Access and someone gave me some advice that got it working.

The problem is that in order to get it to work, Novell has to allow users delete persmissions, which means that they can delete the entire file.

The users don't want the database split so all the data is in one file. What I'm wondering is if I split the database and placed the back-end in a separate folder without delete permissions, would this work since the lock file would be created in the folder with the front-end where they would have delete permissions? Any help would be appreciated. Thanks.

 

[psemianonymous]

Nope, a lockfile is created for any JET database you open, in the same directory as the file itself. This goes for your frontend, your backend, your workgroup file even.

Daily backups are your only good defense against deletions.

 

[AccessHawaii]

Ok, I understand that but what I'm asking is since the lock file is being created in the same directory as the front-end, which is the directory that has delete permissions, which you would need in order to delete the lock file when users enter and exit the database, wouldn't that work if I had the back-end in a separate folder without delete permissions since the lock file wouldn't be created in that directory?

 

[mkov]

There is also a lock file created in the directory where the back-end is located.

 

[AccessHawaii]

That sucks. Theres no way around that with Novell? You're giving the users the ability to delete the entire database, which definitely isn't a good thing.

 

[psemianonymous]

There is an (awful) workaround: give someone, ONE PERSON, create/delete rights on the folder, and have them log on first and log off last. Usually you give your admin-person this right.

The best way to prevent them from deleting the file is to give them a shortcut on their desktop that links to the file. That way, they never have to see your database file in any sort of "delete-enabled" Explorer window.

Also: backups! Can't emphasize enough.

 

[AccessHawaii]

Thanks, but that sounds like too much of a hassle. I always have them access the database through shortcuts because some of the users might be members of several different workgroups. Shortcuts prevent some of the possibility of the file being deleted but you always have those 1 or 2 people who think their the ultimate gurus and they go into the directory and try to make a copy to their hard drive, thinking they can hack into it that way but what they end up doing a lot is dragging and dropping the file into a directory, which removes it entirely and then they can't remember where they placed it.