Tek-Tips is the largest IT community on the Internet today!

Members share and learn making Tek-Tips Forums the best source of peer-reviewed technical information on the Internet!

  • Congratulations IamaSherpa on being selected by the Tek-Tips community for having the most helpful posts in the forums last week. Way to Go!

Db Security

Status
Not open for further replies.

shar

Technical User
Apr 2, 2000
54
IR
In an application I put together, in order to secure the db, I have a bunch of ChangeProperty statements such as &quot;StartupShowDBWindow&quot; and &quot;AllowBreakIntoCode&quot; to false to prevent users to go to the tables directly or to get into the visual basic codes.&nbsp;&nbsp;However, I keep one open (&quot;AllowBypassKey&quot;, True) so that I can get in there for maintenance, code modifications, etc.&nbsp;&nbsp;Is there a better way to handle this?&nbsp;&nbsp;Can I set the &quot;AllowBypassKey&quot; to False with the rest of the properties and still have a way of getting into the system for maintenance?<br><br>Any input would be appreciated.&nbsp;&nbsp;Thanks.<br>
 
Wel ther is a much easier way<br>Create a .MDE from your .MDB<br>First use the Database Splitter<br>Click Tools menu, Add-Ins, Database Splitter<br>This will make a backend of your tables only<br>Then Click Tools menu, Database Utilities<br>Make .MDE<br>This will mkae a compiled version of your .MDB<br>Your users need to run the .MDE<br>and each time you need to make changes then you have to re-create the .MDE<br>This works great I use it alot<br><br>OK<br><br>
 
Status
Not open for further replies.

Part and Inventory Search

Sponsor

Back
Top