Sorry to mislead. By UA, I was referring to UtterAccess.com where I am an administrator. I actually live some distance from Tuscon and Arizona. I'm in Sudbury Ontario (Canada), a little to the northeast of Lake Huron.
Glen, are we neighbors? I'm in Tucson too, if UA means University of Arizona…
In my not so humble opinion, proper planning and designing is far more important than the actual construction (tables, etc.) of the database itself. Jumping in and starting to create the tables before having a comprehensive design based on a detailed needs analysis, is an open invitation to a time consuming exercise in frustration. A colleague of mine at UA has a signature line that goes something like this, shortcuts lead to long delays.
The 80/20 rule is as relevant here as it is elsewhere. Development should be roughly 80% planning, and 20% implementation. The planning component include needs analysis and data analysis. With thorough planning, data definition virtually becomes child's play.
The same goes to developing the user interface (frontend).
I know Crystal has a killer tool for documenting a database that already exists but this is about a green field database. ....starting from scratch.
When one of you pros start designing a new database for a client, do you start by writing up the design (tables, fields, field properties, FKS and relationships to other tables, field comments, etc) or do you just start setting up a dummy set of tables?
Same question for queries, forms, and reports.
This email (and all attachments) is for the sole use of the intended recipient(s) and may contain privileged and/or proprietary information. Any unauthorized review, use, disclosure or distribution is prohibited. If you are not the intended recipient, please contact the sender by reply e-mail and destroy all copies of the original message.
Posted by: "Glenn Lloyd" <email@example.com>
|Reply via web post||•||Reply to sender||•||Reply to group||•||Start a New Topic||•||Messages in this topic (6)|