@pnorsworthy
.
Went one step further. To demo the info you are looking for using my sample, added a query and then a report (simple) based upon that query:
ATVs.odb (17.7 KB)
Wow, Thanks for going to al the trouble. But I think my issues goes deeper than That. I need to enter the Unit number into the form, have it auto populate the Unit Number, VIN, and the description fields. The I will type in or pick from a kist box what goes into the rest of the fields. I have attached what I’ve been working on. it may give you a better Idea. Please note that there are some funky Forms and query’s but you will get the idea
Ratslinger
July 24
@pnorsworthy
.
Went one step further. To demo the info you are looking for using my sample, added a query and then a report (simple) based upon that query:
ATVs.odb (17.7 KB)
TCA Parts Inventory.odb (111 KB)
No, a quick look at your sample confirms what I’ve stated all along. The Unit number is automatically placed on the form (and thus in the record) in my sample. Along with that, and because of it, You do not need the VIN or descriptions fields. These are available any time with a query as I showed in my last sample. It is the feature of relational databases. Coupling records in one table to records in another.
.
Your method has unnecessary duplication of data and not taking advantage of relational databases.
.
Sorry I cannot be of further help because I firmly believe you are taking a wrong direction. Will it work? Yes with a lot of piecemeal parts and the potential for lots of headaches. As to one glaring, for work orders the primary key field is Unit Number & VIN. With a second work order for that unit you will get a duplicate key error. Example: Unit 6 with VIN 3JB1BAX46NK001234. I would think you would have more than one work order for this unit in its’ lifetime. It also appears Unit Number can be a duplicate. Don’t know reason for that but if true my sample would need just simple modification.
Feeling kind of stupid just now. I was thinking, for some reason, that the data base would make a new table for me. That would make the data base redundant. Over thinking the issue. I realize now that joining the two tables together will still store the information I need. Thanks for your help
Ratslinger
July 25
pnorsworthy:
But I think my issues goes deeper than That. I need to enter the Unit number into the form, have it auto populate the Unit Number, VIN, and the description fields.
No, a quick look at your sample confirms what I’ve stated all along. The Unit number is automatically placed on the form (and thus in the record) in my sample. Along with that, and because of it, You do not need the VIN or descriptions fields. These are available any time with a query as I showed in my last sample. It is the feature of relational databases. Coupling records in one table to records in another.
.
Your method has unnecessary duplication of data and not taking advantage of relational databases.
.
Sorry I cannot be of further help because I firmly believe you are taking a wrong direction. Will it work? Yes with a lot of piecemeal parts and the potential for lots of headaches.