Can I force .mdb file to refer to a runtime loader to startup my db if not don't startup
Posted on 2006-03-21
I was warned, that if you have access installed on your computer and you have an access runtime application, you will be able to get to all the rearend objects, sure enough you can.
I was wondering if I could force my .mdb file to refer to the runtime loader the same way it does when you run it from a shortcut with the /runtime switch.
I've noticed the sagekey scripts simply copies my db (.mbd) to a specified directory and then creates a shortcut to it with /runtime switch, If a user that has access installed finds this .mdb file they are capable of doing any thing they wish with it, One good thing if they don't have access installed they will still be able to use the db but not get to design view, to change or modify it.
I'm trying to think of a way a user with access installed will not be able to open my .mdb file so I can keep it safe-guarded?