design help, clueless newbie seeks help

[victoriabitter]

hi all,

I am extremely new to access and building a database for a workshop. reciepe for disaster me thinks.

so I thought it would be best to have two tables,
so if mr smith brings in two jobs there is no need too fill everything out twice in customer table and this way if I need to check previous work history I could query the job ID's for customer numbers.

tables
"customer ID" (info adress's phones and alike)
"JOB ID" (nature of problem , repairs and so on)


I have customer ID Primary key linked as foreign key in JOB id form

is this the right way to design this?? or would it be just better to flatten the whole database out.

so far it seems to be working and everyones impressed and theres hardly anymore paper waste or loss of paper work.



but

when I fill out a new "job Id" I enter the customer number that is related to the the customer ID, Is it possible to get access to automatical insert the customers actual name from the customer ID in job id form. If i can do this everyone at work will declare me god of access (silly buggers)

I hope this makes some sort of sence lol.

thanks and oppologies in advance

[pbaldy]

The two tables sound correct. You don't want to flatten them into one table. As far as the customer name:

http://www.baldyweb.com/Autofill.htm

Noting that you don't want to save the name in the jobs table, just the ID.

[victoriabitter]

thanks paul, I am still thinking that forms are mirror images of tables, I think I am on the right track. the only thing that needs to be related on the job Id is the customer primary/foreign key. and in the form I can "display" what ever fields I like from the customer table. but not save them in the job table
back to reading-lol
4 days ago I knew nothing, now we have a workign database of some description.

thank you thank you thank you.

[pbaldy]

Happy to help. Sometimes it's appropriate to save one of the related values, but not typically.