devtha,
Agreed, if I was concerned with locking tables, I could lock each one. They are locked. The user has no direct access to the table.
They have access through Run With Owner's Permissions queries. I need the mde to be able to run items against these queries, so the user has 'snapshot' settings for the recordset returns, but if you use this, and build a query off a snapshot query, it acts like a normal query (it's a quirk of using qdf's).
I need to *stop the user from making new queries*. The rest is secured properly, only the creation of new queries is the issue.
What you gave me above will lock down permissions on specific *existing* objects. :)
New objects are *supposed* to be controlled via the container, not a document, since the container controls all new objects. Destroying the dbSecCreate permission on the 'Tables' container in 97 removed the ability to create new queries/tables. This is no longer working in Access 2000. I need to know either why, or (preferably) I need a workaround that *will* halt the creation of new queries.
Thanks for the thought, but not what I'm looking for. :(
-Craig
Main Topics
Browse All Topics





by: devthaPosted on 2001-11-21 at 11:24:59ID: 6648416
Try this
tUpdate", True)
bYesNo As Boolean) As Boolean
ents!SysUs erLastUpda te ents(table name)
'Call the function (true will give you permissions)
Call setPermissions("SysUserLas
Public Function setPermissions(tablename$,
Dim db As Database
Dim doc As Document
Set db = CurrentDb()
'Set doc = db.Containers!tables.Docum
Set doc = db.Containers!tables.Docum
doc.UserName = "Admin"
If bYesNo Then
doc.Permissions = dbSecWriteDef Or dbSecRetrieveData Or dbSecInsertData Or dbSecReplaceData Or dbSecDeleteData
Else
doc.Permissions = dbSecRetrieveData
End If