Access restriction

[Housewares]

I have a database that I have put user level security on. When we ship the database, we make the users enter a registration code that tells Access when to expire the database. This works very well. The problem I am having now is that some users tend to write their own software for getting information from the database. Since the database is not being opened in a "conventional" way, the macro that tests whether or not the database is expired never runs. What I need to know is how I can prevent a user from running his third party software to access our information after a certain date has passed, meaning is there any way to set an expiration date for the database that will happen regardless of the methodology used to open the database. Is there a good way to either password protect the database only from SQL or to have code run whenever an SQL query is passed to the database? If anyone has any other ideas on how to limit user access via 3rd party software to one year I would be most grateful.

 

[Housewares]

Thanks for the reply. I suspected that this would be the case. I would appreaciate a link to any software that can do this. Unfortunately the powers that be don;t want an MS SQL database. Maybe this will change their mind.

 

[ghudson]

I have a database that I have put user level security on. The problem I am having now is that some users tend to write their own software for getting information from the database. Since the database is not being opened in a "conventional" way, the macro that tests whether or not the database is expired never runs.

If you db is properly secured using Access security with workgroups and user permissions then nobody shoud be able to access your data unless they log into the db using the correct workgroup and password! Then once they have logged into the db, you are able to set the security to limit what objects they can view or access.

 

[Parker]

If you db is properly secured using Access security with workgroups and user permissions then nobody shoud be able to access your data unless they log into the db using the correct workgroup and password! Then once they have logged into the db, you are able to set the security to limit what objects they can view or access.

Only true to a certain extent.

People often make the mistake of believing that MS software is secure. -- Not true. Most Access security is all too easy to get around without trying to hard.

One of the big problems with security is that if you put a lock on something then someone will always break it just to find out what is there.

If you want to be really secure try wrapping your tables with a third party system like BioLogin -- Short of chopping off someone’s appendages you ain't getting past that without a lot of work (mostly involving Hex editors)

 

[Housewares]

If you db is properly secured using Access security with workgroups and user permissions then nobody shoud be able to access your data unless they log into the db using the correct workgroup and password! Then once they have logged into the db, you are able to set the security to limit what objects they can view or access.

The problem with this is that the user does need to have permission to view certain tables and queries stored in Access - as long as they have a current subscription to the database. The user level security is good for shutting people out of the macros and certain other pieces of information, but does not limit people who should normally be able to log in from logging in after the database has expired.

Unfortunately the option of third-party software isn't availble due to current management. I like Tony's idea of encrypting the database or using an MS SQL database but would that truly remedy the problem? Can what would normally be valid passords after a certain time or at least run some script once they do log in? The problem with encrypting is that they actually like people to have their own software as it usually will convince them to renew their subscripion with us.

Thank you all for your posts and I have found them to be very informative. I just don't see any feasible way to do it and meet all their retarded criteria.

 

[Parker]

Thank you all for your posts and I have found them to be very informative. I just don't see any feasible way to do it and meet all their retarded criteria.

You may have another problem here as well.

You may licence the DB but if the end user has entered data into the tables then they own the data so you must allow them access to it.

IF YOU LOCK THEM OUT OF THE TABLES YOU MAY FIND YOURSELF FALLING FOUL OF THE INTERLECTUAL OWNERSHIP LAWS.

So if you lock them out completely then 'dump' their data as a *.csv on lockout.

If they don't own the data then use a compiled script in VB or C++ to rip the data after a certain date. -------- that will spoil their fun.