In my rearmost eBook on how to make a database, I cover a section about planning your database before inventors should develop it and apply it. Before they know it, it’s too late when they realize how off track they’re and are now left with potentially a reversing and undoing exercise!
So, to get started on the right track then is an excerpt for your reference.
Reverse Engineering? I am frequently asked How do you design a good database? My simple answer, I Reverse mastermind it!
It’s a fashion that I’ve used numerous times and it works veritably well for me. The process to a good
Microsoft Access database design has nothing to do with Microsoft Access or any other database operation.
The methodologies I have come across over time leave me with a lot of questions about” Do the methodologies frequently bandied really justify the end result?”
The quantum of time and complexity of the ways in Microsoft Access database methodologies and system analysis is occasionally a huge outflow of your time and the propositions are occasionally questionable-it may work for others and that is great!
So then is how I start the Reverse Engineering process.
Database planning can ( more so for newbies) shoot you up the wall! But if you spend some time making a task list of the way that will be demanded when you start erecting your Microsoft Access database, checking each item when completed, this will be a good launch and will keep you focused.
But hey, indeed before you class a single character on that keyboard and make your first table, the ensuing process is a pen and paper exercise (or a textbook editor on your computer) and there’s no demand to indeed start-up Access at this point.
Remember, Access is a tool for database operation systems and it’s there to serve as a tool for your processes and not mandate to you how to run your business. So, this composition talks about your processes and how they’ll fit into a structured Microsoft Access database.
I have a 7 step‘ rear engineering’ plan as shown below Microsoft Access database
In fact, the first five-way is critical as they will determine and eventually define the’ back-end database system. The remaining two ways handle the’ frontal– end database system and in some cases, are noway considered as druggies may only wish to work with the’ back– end‘.