|
|
Our Hot Pick: Rising Antivirus 2006 - Certified by TUV & Checkmark! Get 10% discount by entering this coupon code: ONDISCOUNT10
I use a mdw that I join into all my Access databases at work. The problem is
there was an Access database that everyone uses that is in production. I had
to make changes to some forms and reports, so I made a copy of it, and moved
the copy to a different location for development and testing. The copy used
the same mdw as the production database. Everything worked fine in testing,
but when I moved the copied version into production, everyone's access was
messed up. It still used the same mdw as before. Now in testing, I didn't
have any linked tables. But before I moved the test version into production,
I linked all the tables to point to the production data. The production data
is in a seperate Access database.
In the mdw, a while back, there were groups created, and people were
assigned to specific groups. When I went to look at peoples security rights
in the mdb, it showed they were still in the groups assigned to them, but
they could not get to tables, qwueries, forms, report, or macros. Can
someone please let me know what happened, and a quick way to fix this and to
not have this happen again. Any help would be greatly appreciated. I can be
e-mailed at cjelias(remove this)[ at ]lnc.com.
--
Thanks,
Chris
|
|
Could you please be more specific regarding 'everyone's access was messed
up'. that doesn't help us. What error message do they get?
Did you copy the production mdb while it was being used?
The groups that users belong to are not in the database; that information is
contained in the mdw.
During your development and testing, did you at any time import/export any
objects?
--
Joan Wild
Microsoft Access MVP
celias wrote:
[Quoted Text] > I use a mdw that I join into all my Access databases at work. The
> problem is there was an Access database that everyone uses that is in
> production. I had to make changes to some forms and reports, so I
> made a copy of it, and moved the copy to a different location for
> development and testing. The copy used the same mdw as the
> production database. Everything worked fine in testing, but when I
> moved the copied version into production, everyone's access was
> messed up. It still used the same mdw as before. Now in testing, I
> didn't have any linked tables. But before I moved the test version
> into production, I linked all the tables to point to the production
> data. The production data is in a seperate Access database.
>
> In the mdw, a while back, there were groups created, and people were
> assigned to specific groups. When I went to look at peoples security
> rights in the mdb, it showed they were still in the groups assigned
> to them, but they could not get to tables, qwueries, forms, report,
> or macros. Can someone please let me know what happened, and a quick
> way to fix this and to not have this happen again. Any help would be
> greatly appreciated. I can be e-mailed at cjelias(remove
> this)[ at ]lnc.com. --
> Thanks,
> Chris
|
|
Hi Joan,
In regards to your questions, what I meant when I said, "Everyones access
was messed up." was that they had their rights in the groups assigned to
them, but the MDW didn't acknowledge it. I had to go in and mark the check
box for what tables, queries, forms, reports, and macros each user has access
to. This was done by bringing up their personal ID, scrolling down the list
under forms, reports, macros, tables, and queries, and checking from the list
if they only had read access, insert access, delete access, and so on. Once
I did that for every single user, they were fine, but it was very time
consuming.
I re-linked the tables to point to the production tables before I moved the
test version into production.
I've been programming in Access ever since it first came out, and I have
moved programs from a test environment to production more times than I can
count, and this is the first time ever I seen this happen.
Can you please help me.
Thanks,
Chris
I didn't copy the mdb was it was in use.
--
Thanks,
Chris
"Joan Wild" wrote:
[Quoted Text] > Could you please be more specific regarding 'everyone's access was messed
> up'. that doesn't help us. What error message do they get?
>
> Did you copy the production mdb while it was being used?
>
> The groups that users belong to are not in the database; that information is
> contained in the mdw.
>
> During your development and testing, did you at any time import/export any
> objects?
>
>
> --
> Joan Wild
> Microsoft Access MVP
>
> celias wrote:
> > I use a mdw that I join into all my Access databases at work. The
> > problem is there was an Access database that everyone uses that is in
> > production. I had to make changes to some forms and reports, so I
> > made a copy of it, and moved the copy to a different location for
> > development and testing. The copy used the same mdw as the
> > production database. Everything worked fine in testing, but when I
> > moved the copied version into production, everyone's access was
> > messed up. It still used the same mdw as before. Now in testing, I
> > didn't have any linked tables. But before I moved the test version
> > into production, I linked all the tables to point to the production
> > data. The production data is in a seperate Access database.
> >
> > In the mdw, a while back, there were groups created, and people were
> > assigned to specific groups. When I went to look at peoples security
> > rights in the mdb, it showed they were still in the groups assigned
> > to them, but they could not get to tables, qwueries, forms, report,
> > or macros. Can someone please let me know what happened, and a quick
> > way to fix this and to not have this happen again. Any help would be
> > greatly appreciated. I can be e-mailed at cjelias(remove
> > this)[ at ]lnc.com. --
> > Thanks,
> > Chris
>
>
>
|
|
celias wrote:
[Quoted Text] > Hi Joan,
>
> In regards to your questions, what I meant when I said, "Everyones
> access was messed up." was that they had their rights in the groups
> assigned to them, but the MDW didn't acknowledge it.
Sounds as though the wrong mdw was in use.
> I had to go in
> and mark the check box for what tables, queries, forms, reports, and
> macros each user has access to. This was done by bringing up their
> personal ID, scrolling down the list under forms, reports, macros,
> tables, and queries, and checking from the list if they only had read
> access, insert access, delete access, and so on. Once I did that for
> every single user, they were fine, but it was very time consuming.
You shouldn't need to do that for each user. Assigning permissions to the
groups should be sufficient. Remember that these are implicit permissions,
so won't show for each user in the security dialogs.
--
Joan Wild
Microsoft Access MVP
|
|
Hi Joan,
The database is pointing to the same mdw that the old one was pointing to.
I know I shouldn't have to give access to each individual when they are
assigned to a group, but that was the only way they could get into the
database. I guess I'm back to the original questions as to why did all the
users lose their access rights?
--
Thanks,
Chris
"Joan Wild" wrote:
[Quoted Text] > celias wrote:
> > Hi Joan,
> >
> > In regards to your questions, what I meant when I said, "Everyones
> > access was messed up." was that they had their rights in the groups
> > assigned to them, but the MDW didn't acknowledge it.
>
> Sounds as though the wrong mdw was in use.
>
> > I had to go in
> > and mark the check box for what tables, queries, forms, reports, and
> > macros each user has access to. This was done by bringing up their
> > personal ID, scrolling down the list under forms, reports, macros,
> > tables, and queries, and checking from the list if they only had read
> > access, insert access, delete access, and so on. Once I did that for
> > every single user, they were fine, but it was very time consuming.
>
> You shouldn't need to do that for each user. Assigning permissions to the
> groups should be sufficient. Remember that these are implicit permissions,
> so won't show for each user in the security dialogs.
>
>
> --
> Joan Wild
> Microsoft Access MVP
>
>
>
|
|
I have never heard of users/groups losing the permissions in a database.
The only time this happens is if you import/export objects - the permissions
don't travel with the objects.
--
Joan Wild
Microsoft Access MVP
celias wrote:
[Quoted Text] > Hi Joan,
>
> The database is pointing to the same mdw that the old one was
> pointing to. I know I shouldn't have to give access to each
> individual when they are assigned to a group, but that was the only
> way they could get into the database. I guess I'm back to the
> original questions as to why did all the users lose their access
> rights? --
> Thanks,
> Chris
>
>
> "Joan Wild" wrote:
>
>> celias wrote:
>>> Hi Joan,
>>>
>>> In regards to your questions, what I meant when I said, "Everyones
>>> access was messed up." was that they had their rights in the groups
>>> assigned to them, but the MDW didn't acknowledge it.
>>
>> Sounds as though the wrong mdw was in use.
>>
>>> I had to go in
>>> and mark the check box for what tables, queries, forms, reports, and
>>> macros each user has access to. This was done by bringing up their
>>> personal ID, scrolling down the list under forms, reports, macros,
>>> tables, and queries, and checking from the list if they only had
>>> read access, insert access, delete access, and so on. Once I did
>>> that for every single user, they were fine, but it was very time
>>> consuming.
>>
>> You shouldn't need to do that for each user. Assigning permissions
>> to the groups should be sufficient. Remember that these are
>> implicit permissions, so won't show for each user in the security
>> dialogs.
>>
>>
>> --
>> Joan Wild
>> Microsoft Access MVP
|
|
Being that I did link tables into the database to point to live data, and the
permissions didn't apply to the linked tables, how would I go about granting
access using the same mdw that is used in production? Do I have to drop the
mdw from the database in the test environment, link the tables to point to
production, then join the mdw that is used in production, and move the
database from the test environment into production?
--
Thanks,
Chris
"Joan Wild" wrote:
[Quoted Text] > I have never heard of users/groups losing the permissions in a database.
> The only time this happens is if you import/export objects - the permissions
> don't travel with the objects.
>
>
> --
> Joan Wild
> Microsoft Access MVP
>
> celias wrote:
> > Hi Joan,
> >
> > The database is pointing to the same mdw that the old one was
> > pointing to. I know I shouldn't have to give access to each
> > individual when they are assigned to a group, but that was the only
> > way they could get into the database. I guess I'm back to the
> > original questions as to why did all the users lose their access
> > rights? --
> > Thanks,
> > Chris
> >
> >
> > "Joan Wild" wrote:
> >
> >> celias wrote:
> >>> Hi Joan,
> >>>
> >>> In regards to your questions, what I meant when I said, "Everyones
> >>> access was messed up." was that they had their rights in the groups
> >>> assigned to them, but the MDW didn't acknowledge it.
> >>
> >> Sounds as though the wrong mdw was in use.
> >>
> >>> I had to go in
> >>> and mark the check box for what tables, queries, forms, reports, and
> >>> macros each user has access to. This was done by bringing up their
> >>> personal ID, scrolling down the list under forms, reports, macros,
> >>> tables, and queries, and checking from the list if they only had
> >>> read access, insert access, delete access, and so on. Once I did
> >>> that for every single user, they were fine, but it was very time
> >>> consuming.
> >>
> >> You shouldn't need to do that for each user. Assigning permissions
> >> to the groups should be sufficient. Remember that these are
> >> implicit permissions, so won't show for each user in the security
> >> dialogs.
> >>
> >>
> >> --
> >> Joan Wild
> >> Microsoft Access MVP
>
>
>
|
|
Perhaps you are confusing the permissions on the tables in the backend vs.
the permissions on the linked tables in the frontend. They aren't the same.
--
Joan Wild
Microsoft Access MVP
celias wrote:
[Quoted Text] > Being that I did link tables into the database to point to live data,
> and the permissions didn't apply to the linked tables, how would I go
> about granting access using the same mdw that is used in production?
> Do I have to drop the mdw from the database in the test environment,
> link the tables to point to production, then join the mdw that is
> used in production, and move the database from the test environment
> into production? --
> Thanks,
> Chris
>
>
> "Joan Wild" wrote:
>
>> I have never heard of users/groups losing the permissions in a
>> database. The only time this happens is if you import/export objects
>> - the permissions don't travel with the objects.
>>
>>
>> --
>> Joan Wild
>> Microsoft Access MVP
>>
>> celias wrote:
>>> Hi Joan,
>>>
>>> The database is pointing to the same mdw that the old one was
>>> pointing to. I know I shouldn't have to give access to each
>>> individual when they are assigned to a group, but that was the only
>>> way they could get into the database. I guess I'm back to the
>>> original questions as to why did all the users lose their access
>>> rights? --
>>> Thanks,
>>> Chris
>>>
>>>
>>> "Joan Wild" wrote:
>>>
>>>> celias wrote:
>>>>> Hi Joan,
>>>>>
>>>>> In regards to your questions, what I meant when I said, "Everyones
>>>>> access was messed up." was that they had their rights in the
>>>>> groups assigned to them, but the MDW didn't acknowledge it.
>>>>
>>>> Sounds as though the wrong mdw was in use.
>>>>
>>>>> I had to go in
>>>>> and mark the check box for what tables, queries, forms, reports,
>>>>> and macros each user has access to. This was done by bringing up
>>>>> their personal ID, scrolling down the list under forms, reports,
>>>>> macros, tables, and queries, and checking from the list if they
>>>>> only had read access, insert access, delete access, and so on.
>>>>> Once I did that for every single user, they were fine, but it was
>>>>> very time consuming.
>>>>
>>>> You shouldn't need to do that for each user. Assigning permissions
>>>> to the groups should be sufficient. Remember that these are
>>>> implicit permissions, so won't show for each user in the security
>>>> dialogs.
>>>>
>>>>
>>>> --
>>>> Joan Wild
>>>> Microsoft Access MVP
|
|
|