R
Roy Tong
I maintain a shared Access 97 database. I have developed an export
process whereby I use DoCmd.TransferDatabase acExport to copy queries,
forms and selected rows from tables to a subset of the database which
I then send to a remote user who is specifically responsible for that
particular set of data. The user updates the data and returns the
file and I import the data back in.
This works well if the user is on Access 97. However if the user is on
Access 2003 he gets a message saying that he hasn't got permission to
enable the database. It isn't practical to make these users members
of our work group and I don't understand why I should have to as the
Access 97 users aren't members of our work group and it works OK for
them.
I have tried going through the security permissions to give the
standard (non-workgroup) users sufficient access but I still get the
same failure. Is there a particular permission I need to reset that I
might have overlooked?
The newly created export database seems to inherit the security
features from the mother database - is there any way I can prevent
this? i.e. when creating the exported database can I give it its own
new less restrictive set of permissions equivalent to the standard
workgroup file that is put on your hard disk when Access is installed?
process whereby I use DoCmd.TransferDatabase acExport to copy queries,
forms and selected rows from tables to a subset of the database which
I then send to a remote user who is specifically responsible for that
particular set of data. The user updates the data and returns the
file and I import the data back in.
This works well if the user is on Access 97. However if the user is on
Access 2003 he gets a message saying that he hasn't got permission to
enable the database. It isn't practical to make these users members
of our work group and I don't understand why I should have to as the
Access 97 users aren't members of our work group and it works OK for
them.
I have tried going through the security permissions to give the
standard (non-workgroup) users sufficient access but I still get the
same failure. Is there a particular permission I need to reset that I
might have overlooked?
The newly created export database seems to inherit the security
features from the mother database - is there any way I can prevent
this? i.e. when creating the exported database can I give it its own
new less restrictive set of permissions equivalent to the standard
workgroup file that is put on your hard disk when Access is installed?