Starting database

[dave@penneys]

I am starting a home damage claim database for my company that is going to be
used in 10 different hubs all accessing it from HP thin clients off a main
server. I am just a bit above beginner in knowledge so here goes... I know
how to setup the database and i have asked for requests from all the user as
to what they would like to have on the database and i am ready to go. My
question is this: we generate a ticket number for each customer and i would
like to make that my primary key number since it is specific to that customer
and the claim that is generated will be based off that ticket number. If
that is set as the primary key naturally i can't have duplicates in the
table, however we do sometimes get a customer who calls back with additional
damage on the same ticket number my higher ups want the ticket number to have
a -1, -2 after the number, however I tried to exlpain to them that unless you
know there other claims for that ticket one wouldnever know to look for
them... can I insert sub forms off the main form that could be used to add
extra information in the case that the customer calls back with more damage
would that be what sub forms are used for.

thanks

dave

 

[dave@homedeliverygroup]

Also... I know that down the line, even though we went through a thinking
process as to what is needed in the database, there is going to be the need
to update and add new stuff that people think of as they use the database...
What is, or how do you, update the database in the future?

 

[dave@homedeliverygroup]

Thanks for responding Steve just remember that i have a bit more knowledge
then a novice here... so what you are saying about the related tables is that
the "additional" would be just the identical to the main claim table just
with the "additional" added to the name... if that is correct how then do i
tie them togerther and there would be no need for sub forms...? I am
starting to confused and i don't want to be a pain in the butt...

also on the second part of your reply... the HP thin clients have no storage
on them at all... they are all logged on using a web link and the database
that is currenlty accessed resides on a server in Atlanta, we are in Delaware
so there is no where to store anything. Could what you are saying be all
stored to the server that we currenlty access...

thanks

Dave