Quickent way to analyze an ACCESS database
Who is Participating?
Experts Exchange Solution brought to you by
"The solutions and answers provided on Experts Exchange have been extremely helpful to me over the last few years. I wear a lot of hats - Developer, Database Administrator, Help Desk, etc., so I know a lot of things but not a lot about one thing. Experts Exchange gives me answers from people who do know a lot about one thing, in a easy to use platform." -Todd S.
Experts Exchange Solution brought to you by
Facing a tech roadblock? Get the help and guidance you need from experienced professionals who care. Ask your question anytime, anywhere, with no hassle.
Start your 7-day free trialA few more notes...
No product may be able to do this with 100% accuracy.
There may be some objects that are "rarely" used, ...not really "orphaned/not needed"
The same goes for code, ..there may be an old function lurking somewhere in a rarely used module...
In may not be "referenced" anywhere else, ...but it might just be use to get a quick result in the immediate window:
?GetSomeValue(argument1, argument2)
There may also be objects that each of these developers liked to use for some reason/purpose.
Then concern here is that if you could start deleting things that some program says are not "actually being used", then you run the risk of deleting something that very well may be needed.
You may not notice it right away, ...but days/ weeks or months from now, one of these developers will ask about it, or some rarely used functionality fails.
So unless you are creating incremental backups and holding them forever, ...you always run that risk.
If it were me, I wold run the utilities/reports and present the results to the governing body.
I would stop short of recommending what objects to delete.
the database has had at least five other developers working on it and from what I can tell, each basically re-wrote the database but kept all the legacy stuff from the prior developer!To me, this would be a good candidate for a complete re-design, from scratch.
Too many cooks in the kitchen,
Finally it is not clear what your role is here in all of this?
New Head Chef, ...or just another cook...?
;-)
JeffCoachman
It's more than this solution.Get answers and train to solve all your tech problems - anytime, anywhere.Try it for free Edge Out The Competitionfor your dream job with proven skills and certifications.Get started today Stand Outas the employee with proven skills.Start learning today for free Move Your Career Forwardwith certification training in the latest technologies.Start your trial today
From novice to tech pro — start learning today.
Experts Exchange Solution brought to you by
That being the case, I would focus on the changes they are looking for. I use Rick Fischer's Find & Replaceto find all instances of an objects use before making any changes to that object. But if you only have two weeks, there is no way you are going to fully understand a complicated application prior to making changes.
FMS's Total Access Analyzer will also produce an extensive report on the use (and orphaned status of various objects), but it is likely to be even longer than the documentor report. Although you can filter on only the orphaned items.