Track changes to database design

30 Mar 2006 9:02 PM

dreamsoul620 via AccessMonster.com

Hi,

I am currently tracking the user's logon name. We have a few over ambitious
users that are finding ways to change the actual design of forms, queries,
and reports. This causes quite a few problems. With so many different users,
we cannot place blame on just one person. Is there a way to track the
changes made along with the username and current date? At least if I know
who is making the changes, we could find out how they are getting into design
view to begin with.

Thanks,
Crystal

--
To be the best, you have to first give up everything.

Message posted via AccessMonster.com
http://www.accessmonster.com/Uwe/Forums.aspx/access-security/200603/1

30 Mar 2006 9:38 PM

Immanuel Sibero

Hi Crystal,

There may be away but wouldnt it be a band aid approach to your issue?
If I'm reading you correctly, you're trying to find a way to track usage so
that now you would know who to blame. Wouldnt this mean that you would still
have problems with unwanted/bad design changes? Sure, you would now know who
did it, and you would slap his wrist or cut off his fingers so he would
never type again. But you would still end up having to correct the design
changes.

You should limit design to designers. How about coordinating the process
where:
- only designers can make design changes (pick your most qualified user or
users to be in this group)
- discussion and approval process before design changes are implemented
- there are ways to restrict regular users from getting into the design mode

This way all design changes can be maintained and controlled. Heck, there
wouldn't even be a need track usage so you can find who to blame.

HTH,
Immanuel Sibero

"dreamsoul620 via AccessMonster.com" <u18823@uwe> wrote in message

news:5e0b77b0b185b@uwe...
Show quoteHide quote

> Hi,
>
> I am currently tracking the user's logon name. We have a few over
ambitious
> users that are finding ways to change the actual design of forms, queries,
> and reports. This causes quite a few problems. With so many different
users,
> we cannot place blame on just one person. Is there a way to track the
> changes made along with the username and current date? At least if I know
> who is making the changes, we could find out how they are getting into
design
> view to begin with.
>
> Thanks,
> Crystal
>
> --
> To be the best, you have to first give up everything.
>
> Message posted via AccessMonster.com
> http://www.accessmonster.com/Uwe/Forums.aspx/access-security/200603/1

31 Mar 2006 7:33 PM

dreamsoul620 via AccessMonster.com

I agree with you're saying. I already have limited the usage so that design
view is hidden from all users but Admin. And I'm the only one in that group.
It would be nice to know if someone has the Admin password or has found a way
around the system. Everyone else has a link. The main database is located
in a hidden folder on the server. The links display a switchboard and a
custom menu bar. The other menus are set to Do not display full menu, so
that the Modes are not listed under Edit or even if you right click. Yet,
changes are still being made and I know that I'm not the one responsible.
Any ideas?

Immanuel Sibero wrote:
Show quoteHide quote

>Hi Crystal,
>
>There may be away but wouldnt it be a band aid approach to your issue?
>If I'm reading you correctly, you're trying to find a way to track usage so
>that now you would know who to blame. Wouldnt this mean that you would still
>have problems with unwanted/bad design changes? Sure, you would now know who
>did it, and you would slap his wrist or cut off his fingers so he would
>never type again. But you would still end up having to correct the design
>changes.
>
>You should limit design to designers. How about coordinating the process
>where:
>- only designers can make design changes (pick your most qualified user or
>users to be in this group)
>- discussion and approval process before design changes are implemented
>- there are ways to restrict regular users from getting into the design mode
>
>This way all design changes can be maintained and controlled. Heck, there
>wouldn't even be a need track usage so you can find who to blame.
>
>HTH,
>Immanuel Sibero
>
>> Hi,
>>
>[quoted text clipped - 8 lines]
>> Thanks,
>> Crystal

--
To be the best, you have to first give up everything.

Message posted via AccessMonster.com
http://www.accessmonster.com/Uwe/Forums.aspx/access-security/200603/1

31 Mar 2006 8:04 PM

Joan Wild

Have you disabled the shiftkey bypass?

Perhaps someone is just holding down the shiftkey when they open it.

--
Joan Wild
Microsoft Access MVP

dreamsoul620 via AccessMonster.com wrote:

Show quoteHide quote

> I agree with you're saying. I already have limited the usage so that
> design view is hidden from all users but Admin. And I'm the only one
> in that group. It would be nice to know if someone has the Admin
> password or has found a way around the system. Everyone else has a
> link. The main database is located in a hidden folder on the server.
> The links display a switchboard and a custom menu bar. The other
> menus are set to Do not display full menu, so that the Modes are not
> listed under Edit or even if you right click. Yet, changes are still
> being made and I know that I'm not the one responsible. Any ideas?
>
> Immanuel Sibero wrote:
>> Hi Crystal,
>>
>> There may be away but wouldnt it be a band aid approach to your
>> issue?
>> If I'm reading you correctly, you're trying to find a way to track
>> usage so that now you would know who to blame. Wouldnt this mean
>> that you would still have problems with unwanted/bad design changes?
>> Sure, you would now know who did it, and you would slap his wrist or
>> cut off his fingers so he would never type again. But you would
>> still end up having to correct the design changes.
>>
>> You should limit design to designers. How about coordinating the
>> process where:
>> - only designers can make design changes (pick your most qualified
>> user or users to be in this group)
>> - discussion and approval process before design changes are
>> implemented
>> - there are ways to restrict regular users from getting into the
>> design mode
>>
>> This way all design changes can be maintained and controlled. Heck,
>> there wouldn't even be a need track usage so you can find who to
>> blame.
>>
>> HTH,
>> Immanuel Sibero
>>
>>> Hi,
>>>
>> [quoted text clipped - 8 lines]
>>> Thanks,
>>> Crystal
>
> --
> To be the best, you have to first give up everything.
>
> Message posted via AccessMonster.com
> http://www.accessmonster.com/Uwe/Forums.aspx/access-security/200603/1

30 Mar 2006 10:26 PM

tina

i agree with Immanuel; it's far better to prevent users from changing the
structure of your db at will, than to find ways to mop up the mess. first,
since your database has multiple users, it should be split into a backend
(tables only) and a frontend (all other objects), with the backend placed on
the common server, and its' tables linked to the frontend. a "master" copy
of the frontend db should be kept by the developer for subsequent
fixes/enhancements; the "production" frontend should be converted to a .mde
file and a copy of same loaded to each user's PC. the .mde file will protect
the structure of forms, reports, and VBA. to protect the structure of
queries, macros, and the tables/data, you can do various things to restrict
access to the database window; however, if you have one or more very
"Access-savvy" users, the best way to protect the whole database is by
implementing user-level security.

hth

"dreamsoul620 via AccessMonster.com" <u18823@uwe> wrote in message

news:5e0b77b0b185b@uwe...
Show quoteHide quote

> Hi,
>
> I am currently tracking the user's logon name. We have a few over
ambitious
> users that are finding ways to change the actual design of forms, queries,
> and reports. This causes quite a few problems. With so many different
users,
> we cannot place blame on just one person. Is there a way to track the
> changes made along with the username and current date? At least if I know
> who is making the changes, we could find out how they are getting into
design
> view to begin with.
>
> Thanks,
> Crystal
>
> --
> To be the best, you have to first give up everything.
>
> Message posted via AccessMonster.com
> http://www.accessmonster.com/Uwe/Forums.aspx/access-security/200603/1