protecting a database

  • Thread starter Thread starter JethroUK©
  • Start date Start date
J

JethroUK©

i've spent my own time creating a database front end (forms, reports, mail
merges, coding & custom functions, etc) for use by staff for my benefit
only - it's wrapped up 80% of my paperwork

i quite happy to leave back end (data tables) wide open for the company to
use as they see fit, but i want to protect the front end forms (my work)

is there a simple efficient way to protect them against use without my
permission over the long term - staff entering a new password every time
they use it is not realist option, either for the staff or me - but a
password once every 3 months or so

any ideas
 
i quite happy to leave back end (data tables) wide open for the company to
use as they see fit, but i want to protect the front end forms (my work)
Click to expand...

Make a .MDE file from the database; keep the .mdb file under lock and
key, and distribute the MDE. The forms and code will not be editable.

John W. Vinson[MVP]
 
John Vinson said:
Make a .MDE file from the database; keep the .mdb file under lock and
key, and distribute the MDE. The forms and code will not be editable.

John W. Vinson[MVP]
Click to expand...

whilst this would stop them editing it - it wouldn't stop them using it
without my permission - i'm thinking of a coding answer - something that
'times out' every 3 months without my express permission keeping the usage
open
 
Back
Top