Restricting User's Access to Database

[Victoria]

Hello,

I have created an order entry database with switchboard that is linked
to two forms and a bunch of reports. I have send it to about 30 users
to test it out with everything in the startup menu of the dabase
turned off except for my custom menu. I have found that although we
are all running Acess 2000. some users were experiencing problems,
specifically it seemed that one of the objects in my liblary Microsoft
Access Excel 11.0 was not available on their computer, the latest
version was 10.0. I fixed the problem using my collegue's computer
which also was missing object 11.0.

I would like to know if there was a way to package my database or
split it off so that the end user 1. only sees the forms and has no
access to database itselft. The problem with startup is that the user
can still open the database in a safemode and see the all the tables,
modules, ect. 2. That it works on their computer regardless of what
kind of object liblary they have.

Any suggestions?

Thank you,
Victoria

 

[alex]

Hello,

I have created an order entry database with switchboard that is linked
to two forms and a bunch of reports. I have send it to about 30 users
to test it out with everything in the startup menu of the dabase
turned off except for my custom menu. I have found that although we
are all running Acess 2000. some users were experiencing problems,
specifically it seemed that one of the objects in my liblary Microsoft
Access Excel 11.0 was not available on their computer, the latest
version was 10.0. I fixed the problem using my collegue's computer
which also was missing object 11.0.

I would like to know if there was a way to package my database or
split it off so that the end user 1. only sees the forms and has no
access to database itselft. The problem with startup is that the user
can still open the database in a safemode and see the all the tables,
modules, ect. 2. That it works on their computer regardless of what
kind of object liblary they have.

Any suggestions?

Thank you,
Victoria

Victoria,

There's a way to split your database so that the forms, reports, etc
are in one location
and your tables in another.

Tools>Database Utilities>Database Spitter

This will seperate the two as aforementioned and link your tables in a
location of your choosing.
That may not answer all your questions but HTH.

alex

 

[Tony Toews [MVP]]

I have created an order entry database with switchboard that is linked
to two forms and a bunch of reports. I have send it to about 30 users
to test it out with everything in the startup menu of the dabase
turned off except for my custom menu. I have found that although we
are all running Acess 2000. some users were experiencing problems,
specifically it seemed that one of the objects in my liblary Microsoft
Access Excel 11.0 was not available on their computer, the latest
version was 10.0. I fixed the problem using my collegue's computer
which also was missing object 11.0.

I would like to know if there was a way to package my database or
split it off so that the end user 1. only sees the forms and has no
access to database itselft. The problem with startup is that the user
can still open the database in a safemode and see the all the tables,
modules, ect.

Make your system into an MDE and then turn off the shift key so that
they can't start up the database without executing your startup form.
I think there's one or two other things you need to do but I forget
what they are.

If you make an MDE you must *always* retain the MDB so you can
continue to work in it.

2. That it works on their computer regardless of what
kind of object liblary they have.

Late binding means you can safely remove the reference and only have
an error when the app executes lines of code in question. Rather than
erroring out while starting up the app and not allowing the users in
the app at all. Or when hitting a mid, left or trim function call.

You'll want to install the reference if you are programming or
debugging and want to use the object intellisense while in the VBA
editor. Then,. once your app is running smoothly, remove the
reference and setup the late binding statements.

Sample code:
' Declare an object variable to hold the object
' reference. Dim as Object causes late binding.
Dim objWordDoc As Object
Set objWordDoc = CreateObject(" Word.Document")

For more information including additional text and some detailed links
see the "Late Binding in Microsoft Access" page at
http://www.granite.ab.ca/access/latebinding.htm

Tony
--
Tony Toews, Microsoft Access MVP
Please respond only in the newsgroups so that others can
read the entire thread of messages.
Microsoft Access Links, Hints, Tips & Accounting Systems at
http://www.granite.ab.ca/accsmstr.htm