D
dt01pqt_pt
I am using access 97. I have just finished making a database. I us
currentUser to log the current user and provide their custom settings
I don't have a problem with programming but I'm new to data basin
(other than data loading) especially access. I need there to be lots o
users in the users group and 1 admin with admins & users.
successfully managed to lock the users group out of the editing o
reading the design of 2 forms. I wanted admin to own both the forms an
have full control of the forms and tables, etc. When I changed the mai
form owner to admin, I couldn't make these changed on the other form o
indeed edit it. The owner in the second form is <unknown> which is th
default. I'm locked out of my own form design boo
. This second for
can be run independently but is usually opened from notInList even
where data from the main form is passed to the other form and entere
in it's only table extending the dropdown list in the main form, an
storing other details in the table. However I don't think this shoul
make any difference to the access rights. So am I screwed?
I do have a copy of the database before fiddling with security so
could import the more current main form into this database, but woul
take time to get it back to how it was.
What kind of stupidity is the concept of owner <unknown>, wher
ownership is either assigned or not? How about <none> o
anti-ownership? That would make more sense
currentUser to log the current user and provide their custom settings
I don't have a problem with programming but I'm new to data basin
(other than data loading) especially access. I need there to be lots o
users in the users group and 1 admin with admins & users.
successfully managed to lock the users group out of the editing o
reading the design of 2 forms. I wanted admin to own both the forms an
have full control of the forms and tables, etc. When I changed the mai
form owner to admin, I couldn't make these changed on the other form o
indeed edit it. The owner in the second form is <unknown> which is th
default. I'm locked out of my own form design boo
. This second forcan be run independently but is usually opened from notInList even
where data from the main form is passed to the other form and entere
in it's only table extending the dropdown list in the main form, an
storing other details in the table. However I don't think this shoul
make any difference to the access rights. So am I screwed?
I do have a copy of the database before fiddling with security so
could import the more current main form into this database, but woul
take time to get it back to how it was.
What kind of stupidity is the concept of owner <unknown>, wher
ownership is either assigned or not? How about <none> o
anti-ownership? That would make more sense