I have been struggling with a problem that concerns users 
being able to create a new database and import or link to 
tables in a user level "secured" database.  If I set the 
user permissions high enough to allow them to add, edit 
and delete through a form "layer", these permissions also 
allow them to link and import tables to a new database- 
which I don't want them to be able to do.  Since I can't 
find any info in the MS security faq that relates to this, 
I have been considering using hidden objects as a 
security measure:

Function MakeHiddenAttachedTable()
Dim strDatabaseName As String
Dim strTableName As String
Dim strAttachedTablename As String
Dim idxNew As Index

Dim DB As Database
Dim td As TableDef

Set DB = CurrentDb
strDatabaseName <ODBC string/database>


Set td = DB.CreateTableDef("<tablename>")
    td.Connect = strDatabaseName
    td.SourceTableName = "<tablename>"
    DB.TableDefs.Append td
    td.Attributes = dbHiddenObject

End Function

This hides the table without users being able to see by simply
clicking the show hidden tables check box, but when I run a 
compact and repair, this type of hidden table is no longer 
contained in the database!!!!

Any suggestions/comments pertaining to using the 
dbHiddenObject attribute for security or what happens to 
those objects during compact and repair is appreciated greatly.

LH