Managing changes to MS Access reports

[MSPLearner]

We have a group of casual MS Access users, who over time created some useful
operational reports - these are useful/critical reports so we need to manage
changes carefully. What are the best practices that one should follow with
the MS Access environment. Right now, each user has their own instance of MS
Access that connects to the back end DB (All MS Access tables link to back
end SQL Server).

MSPLearner

 

[Jeff Boyce]

You didn't mention (specifically) where the front-end is... is that what you
were referring to with "has their own instance of MS Access..."?

Where are these casual users storing their reports? In their own
"front-end" instance on their own PC?

If so, what's the problem? No, seriously, what business issue or problem
are you trying to solve? "How" will depend on "what".

Regards

Jeff Boyce
Microsoft Office/Access MVP

 

[MSPLearner]

Jeff,

Each casual user stores reports on their own instance/PC. These reports are
created/provided for outside users/customers.

So as a manager, I need to make sure that if the employee disappears
tommorow , who would run a particular report, is there an audit trail of
changes being made to report based on new requirements, demands. What about
in-advertant or malicious changes? It's a similar issue as managing software
changes in a development environment - why get concerned about who is making
what change to what component?

 

[Jeff Boyce]

I'm still not clear on how you'd 'herd cats' ... if each user has his/her
own reports, how are you supervising/collecting them together now? How are
you documenting the audit trail now? Are the individual users documenting
their own changes already, or do you need them to document first, before you
can consolidate?

If you are actually looking at change management, you might have to force
the users to use a change management tool, and check-out the application,
make their changes, do their documentation, and check the whole lot back in.
That way, changes would be hosted in a central location... but only one can
make changes at a time...

Is that closer to what you are trying to accomplish?

Regards

Jeff Boyce
Microsoft Office/Access MVP