How to keep from entering an Id and password

  • Thread starter Thread starter Guest
  • Start date Start date
G

Guest

Have FE/BE Access 2003 database that I want to use user level security and
would like to have the application start without requiring users to enter an
id and password (I plan on distributing to a varied user group) but at the
same time only allow them to read/update data - not make an other
changes....is this possible, if so how?

Thanks

Jerry
 
JWS315 said:
Have FE/BE Access 2003 database that I want to use user level
security and would like to have the application start without
requiring users to enter an id and password (I plan on distributing
to a varied user group) but at the same time only allow them to
read/update data - not make an other changes....is this possible, if
so how?

Thanks

Jerry
Click to expand...

Instead of giving the default user "Admin" and the default group "Users" zero
permissions (as you normally would when applying security), give "Users"
whatever read only access you desire for your target audience. They will get
those permissions without needing a special workgroup and thus without having to
log in.
 
Once I do this is there a way to also "login" to a BE database in vba code
with an Admins id that will allow the adding of tables and fields without
having to use a different mdw file? I want to try and maintain my tables in
the BE via the FE in vba so that when I have a change in structure (new
table, relationships, index, fields) I can just distribute a new FE that will
update the BE.

Thanks for the quick response!

Jerry
 
JWS315 said:
Once I do this is there a way to also "login" to a BE database in vba
code with an Admins id that will allow the adding of tables and
fields without having to use a different mdw file? I want to try and
maintain my tables in the BE via the FE in vba so that when I have a
change in structure (new table, relationships, index, fields) I can
just distribute a new FE that will update the BE.

Thanks for the quick response!
Click to expand...

Nope. You can (in code) instantiate another workspace using a different user
that has higher permissions, but you would have to do that while specifying a
secure MDW file as the workgroup.
 
So I could have my users startup with the default system.mdw and then supply
another secure mdw that I would use to modify the BE -

Here is some code that I was working on to do something like that - but not
sure how to login to the database using the secure mdw with the Admin id &
password - I assume the "owner" of any new tables would be the Admin id?

Set dbPrevCon= DBEngine.OpenDatabase(strFileName, False, False, "MS
Access;pwd=iaslocv43")
Set tdfGlossary = dbPrevCon.CreateTableDef("Glossary")
With tdfGlossary
.Fields.Append .CreateField("Organization", dbText, 50)
.Fields.Append .CreateField("Acyn", dbText, 8)
.Fields.Append .CreateField("AcynDesc", dbMemo)
End With
dbPrevCon.TableDefs.Append tdfGlossary
For Each Fld In tdfGlossary.Fields
If Fld.Name = "Organization" Then
Fld.Required = True
End If
If Fld.Name = "Acyn" Then
Fld.Required = True
End If
Next
dbPrevCon.TableDefs.Refresh
Set con = dbPrevCon.Containers!Tables
Set doc = con("Glossary")
doc.UserName = "Admin"
doc.Permissions = dbSecInsertData Or dbSecReplaceData Or
dbSecRetrieveData Or dbSecDeleteData

Thanks!!

Jerry
 
JWS315 said:
So I could have my users startup with the default system.mdw and then
supply another secure mdw that I would use to modify the BE -

Here is some code that I was working on to do something like that -
but not sure how to login to the database using the secure mdw with
the Admin id & password - I assume the "owner" of any new tables
would be the Admin id?
Click to expand...

If you're going to distribute a secure MDW just have your users use that. As
long as you don't give the user "Admin" a password they will still log in
without a prompt as that user and as a member of "Users" as previously
discussed. Then when you instantiate a new workspace you don't have to specify
a different mdw file.
 
Ok - but how do I login using the id in the Admins group that will allow my
vba code to add tables, fields, etc? How do I instantiate a new workspace
that uses the higher security level id for the BE maintance?
 
JWS315 said:
Ok - but how do I login using the id in the Admins group that will
allow my vba code to add tables, fields, etc? How do I instantiate a
new workspace that uses the higher security level id for the BE
maintance?
Click to expand...

I must admit that I have never done it, but from the help file I assume one
would use...

CreateWorkspace Method
Creates a new Workspace object.

Syntax
Set workspace = CreateWorkspace(name, user, password, type)
 
Back
Top