ednde22
January 20th, 2000, 07:48 AM
Hello,
We are using a database written in FoxPro running on NT SP4 with 50+ users. This database creates an .in file whenever a user enters the database and when they leave the system removes the .in file. This is how the system knows how many users are logged into the database. We only have 20 licenses and additional license purchases are very expensive. My problem is that users will delete other user's .in file so that they can access the DB. I tried setting the rights to RWX and not delete but the DB needs to have this active so that it can remove the .in file. Any suggestions on how I can prevent the user's from deleting this file. Can i map this drive and make it hidden? If so, how and what are the ramifications of this? Thanks for the help.
We are using a database written in FoxPro running on NT SP4 with 50+ users. This database creates an .in file whenever a user enters the database and when they leave the system removes the .in file. This is how the system knows how many users are logged into the database. We only have 20 licenses and additional license purchases are very expensive. My problem is that users will delete other user's .in file so that they can access the DB. I tried setting the rights to RWX and not delete but the DB needs to have this active so that it can remove the .in file. Any suggestions on how I can prevent the user's from deleting this file. Can i map this drive and make it hidden? If so, how and what are the ramifications of this? Thanks for the help.