Re: The agony of building an Application
- From: RD <progr@xxxxxxxxx>
- Date: Wed, 02 Aug 2006 10:59:50 -0700
Hi Sreedhar,
You've received some excellent advice from better heads than mine but I thought
I'd jump in anyway. :-)
I started with Acc95 and a book. Almost all the books will cover the basics of
good database design and some of them also talk about good application design.
Since then my learning has all been the "old fashioned" way. I went out and
made mistakes. Don't worry about "awkward code. Finesse and elegance will come
with time and practice. I'm always looking for a better way to do something
I've done a hundred times.
You mention beating your head against a wall looking at old code. One thing I
learned early on is to comment the heck out of my code. I recently met up with
an old tech lead of mine from a project I left back in '01. He had kept most of
the code from that project and allowed me to download it onto my data stick.
Even with some of the far out stuff I was doing back then, reading my code was
made much more easy because of the copious commenting I did.
Some suggested books:
Building Access Applications - John L. Viescas - Microsoft Press
Access 2003 Bible - Prague, Irwin and Reardon - Wiley Press
Access 2003 VBA - Cardoza, Hennig, Seach and Stein - Wrox
Fixing Access Annoyances - Mitchell and Callahan - O'Reilly
Have fun!
RD
On Sat, 29 Jul 2006 08:45:02 -0700, Sreedhar
<Sreedhar@xxxxxxxxxxxxxxxxxxxxxxxxx> wrote:
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 ?
.
- Prev by Date: Re: Inherited code keeps re-running
- Next by Date: Re: Date() Function not available - Name conflict
- Previous by thread: Re: The agony of building an Application
- Next by thread: Filehandling error
- Index(es):
Relevant Pages
|
Loading
