Re: Is this a Sound Database Design? -- Table Structure comments

ps

you DID ask if you had a sound database design...


Warm Regards,
Crystal
*
(: have an awesome day :)
*
MVP Access
Remote programming and Training
strive4peace2006 at yahoo.com
*



Curtis Stevens wrote:
The issue is I have an online app and it sends me everything to my email, which I then import or paste into the database. This online app has a good 80% of the fields in my main table, so I can't just go splitting everything up. I have it tab delimited in the email, so I just select all of it, copy & paste. I will never have it feed directly into the db on a server, as to me, you rely too much on that server to be up 24/7, etc. I have my confidnence in Unix & having it emailed or sent electronically to me, etc.


MORE:


Keep in mind how long your data is and name your fields accordingly (since you can't wrap fieldnames)

for instance:
Trouble Ticket ID --> TrouTickID

Why not just have TroubleTicketID? What is wrong with that long of a name, so you know what it is exactly & easily?

Keep names short (you will appreciate this when you write code). Users do not need to concern themselves with cryptic names -- use the field description to get more descriptive and do not use captions in the table design.

You mean in design view, when you select a field, not the caption box below? Why is that?

Curtis

.