Protecing Design View on an ADP

[desireemm]

Hi all I am working off an ADP (SqL Server 2005 as Engine) and I know I can
take creating rights away from users on sql but I dont want them to access to
the design view of the forms, how would protect the design view of a form??

 

[Banana]

Never used ADP, but I'm pretty sure ADP supports conversion into a
compiled form that is noneditable, converting ADP into a ADE, just much
like a MDB would convert into MDE.

Of course, make a backup and always keep a copy of original ADP because
ADE (as well as MDE) is noneditable and the operation is irreversible.

 

[Sylvain Lafontaine]

In the same way that you can creat a MDE or ACCDE protected from a MDB or
ACCDB database file, you can create an ADE file from an ADP project.
However, you will also be plagued with the same endless list of problems
that comes with MDE and ACCDE files when you'll try to distribute your ADE
file to user who won't have the exact same configuration (version of Access,
Windows and/of Service Packs) as you.

--
Sylvain Lafontaine, ing.
MVP - Windows Live Platform
Email: sylvain2009 sylvainlafontaine com (fill the blanks, no spam please)
Independent consultant and remote programming for Access and SQL-Server
(French)

 

[S.Clark]

You could implement full bore Access User Level Security on it, but I compare
it to waterboarding.

Another concept would be to prevent the user from getting to the dbWindow
and restrict the menus, then they could get to design view. For example, set
the option to hide the database window and full menus, and then also disable
the show database window key and the bypass(Shift)
key(http://www.bing.com/search?q=AllowByPassKey). These things are far more
simple, and do a good job of keeping out the Nosy Nellies.

 

[desireemm]

Ok I looked on MS website on Allowbypass here is what I saw, apparently I am
suppose to put the code. sorry I'm not a programmer wish I was

http://office.microsoft.com/en-us/access/HA012327171033.aspx

Sub SetBypassProperty()
Const DB_Boolean As Long = 1
ChangeProperty "AllowBypassKey", DB_Boolean, False
End Sub

Function ChangeProperty(strPropName As String, _
varPropType As Variant, _
varPropValue As Variant) As Integer

Dim dbs As Object, prp As Variant
Const conPropNotFoundError = 3270

Set dbs = CurrentDb
On Error GoTo Change_Err
dbs.Properties(strPropName) = varPropValue
ChangeProperty = True

Change_Bye:
Exit Function

Change_Err:
If Err = conPropNotFoundError Then ' Property not found.
Set prp = dbs.CreateProperty(strPropName, _
varPropType, varPropValue)
dbs.Properties.Append prp
Resume Next
Else
' Unknown error.
ChangeProperty = False
Resume Change_Bye
End If
End Function

 

[S.Clark]

Congrats on your promotion... you are now.

Just copy and paste that code into a module, then run it to either turn it

 

[desireemm]

I did that and it gave me an error message saying Invalid outside of procedure
and its highlighting "AllowBypassKey". What am I doing wrong??

Const DB_Boolean As Long = 1
ChangeProperty "AllowBypassKey", DB_Boolean, False
End Sub

 

[S.Clark]

looks like you missed the header:

Sub SetBypassProperty()