G
Guest
I created an Access 2003 database and added user-level passwords. One level
is for me (administrator), another for design/data changes and a 3rd for
read-only.
Access created a shortcut on my desktop that I copied to a folder on the
server where the database resides.
The good thing is that those in the office on 2003 can get into it correctly
by using passwords when they dbl-clk on the shortcut icon.
However. those using Access 2000 can't! BUT, they CAN click directly on the
application icon and open it without password dialog popping up. Unacceptable!
What I did, albeit less that ideal, is create a separate folder on the
server where each week a copy from the previous week will be posted for those
read-only folks using 2000 AND the icon for 2003 users who can go in and look
at the LIVE version but forced to use passwords. (Access 97 won't open it at
all but it doesn't matter since the few people who use 97 won't be using the
database anyway.
We'd like to use this database in both 2000 AND 2003. Any thoughts on what I
can do to do this short of forcing everyone to use 2003? That solution would
take longer than is acceptable...
pls advise...thanx! Don
is for me (administrator), another for design/data changes and a 3rd for
read-only.
Access created a shortcut on my desktop that I copied to a folder on the
server where the database resides.
The good thing is that those in the office on 2003 can get into it correctly
by using passwords when they dbl-clk on the shortcut icon.
However. those using Access 2000 can't! BUT, they CAN click directly on the
application icon and open it without password dialog popping up. Unacceptable!
What I did, albeit less that ideal, is create a separate folder on the
server where each week a copy from the previous week will be posted for those
read-only folks using 2000 AND the icon for 2003 users who can go in and look
at the LIVE version but forced to use passwords. (Access 97 won't open it at
all but it doesn't matter since the few people who use 97 won't be using the
database anyway.
We'd like to use this database in both 2000 AND 2003. Any thoughts on what I
can do to do this short of forcing everyone to use 2003? That solution would
take longer than is acceptable...
pls advise...thanx! Don