G
Guest
This post is not about any specific issue but about building the Application
itself. Please have patience to read the tale of an ametuer "programmer(?)".
Please help if it sounds meaningful.
Three months ago, when I was first exposed to Access, I was amazed to see
the ease with which one can build databases. I was hooked and started by
building my own Application. Learning VBA further enhanced the functionality
of my db.
The problem now is:
The code I wrote initially was very awkward. As I got more and more
acquainted with VBA and its possibilities (still exploring), my Application
grew in size and utility and is fairly successful in meeting the objectives I
set out at the beginning BUT it all became bits and pieces - a modification
here and an improvement there !
So I have decided to re-build a comprehensive Database with enhanced
features and started looking at Sample dbs and I am more confused than ever.
Also, re-writing the code is not as simple as I thought - sometimes, I'm
beating my head against a wall to find what went in my mind when I wrote that
in the past.
Ok, the question is:
Is there any standard documentation or blue-print that answers the following
questions and acts like a checklist ?
How should I approach when I set out to build an Access Application ?
How should I translate my objectives into what should be done with Access ?
How to make sure I don't miss anything ? (and avoid the agony of doing it
all again)
How to know what IS possible and NOT possible with Access ? (and avoid that
"errr... I should have added this to my db!" feeling)
What is the reasonable time it takes to build a feature-rich Access db?
What are the best practices to do it ?
itself. Please have patience to read the tale of an ametuer "programmer(?)".
Please help if it sounds meaningful.
Three months ago, when I was first exposed to Access, I was amazed to see
the ease with which one can build databases. I was hooked and started by
building my own Application. Learning VBA further enhanced the functionality
of my db.
The problem now is:
The code I wrote initially was very awkward. As I got more and more
acquainted with VBA and its possibilities (still exploring), my Application
grew in size and utility and is fairly successful in meeting the objectives I
set out at the beginning BUT it all became bits and pieces - a modification
here and an improvement there !
So I have decided to re-build a comprehensive Database with enhanced
features and started looking at Sample dbs and I am more confused than ever.
Also, re-writing the code is not as simple as I thought - sometimes, I'm
beating my head against a wall to find what went in my mind when I wrote that
in the past.
Ok, the question is:
Is there any standard documentation or blue-print that answers the following
questions and acts like a checklist ?
How should I approach when I set out to build an Access Application ?
How should I translate my objectives into what should be done with Access ?
How to make sure I don't miss anything ? (and avoid the agony of doing it
all again)
How to know what IS possible and NOT possible with Access ? (and avoid that
"errr... I should have added this to my db!" feeling)
What is the reasonable time it takes to build a feature-rich Access db?
What are the best practices to do it ?