relationships and form usage issue

[sully944]

Hi, I'm new to this and I'm ironing out some issues with my planning. I would like to use the tblvehrecovery which is linked to a form frmrecovery which will collect data from the attached tables. contact and phone in this case would only be a text field and not added to the contact table which does exist. Once this form creates a new record that record will need to be updated with status changes. Should I add and order table to facilitate this transaction?

[isladogs]

Welcome to the forum

I think you can dramatically simplify this as I think you are 'over normalising'.
There are 9 tables with a PK field and one other field.
There are another 2 tables with a PK field ONLY.
It's unlikely you need to store these separately.
If so, scrap most or all of those tables

For example tblLicenseID - enter the value using a form and save in tblVehicleInfo.
Suggest you remove the underscore.

Use a query if you need to get a list of licence plate values.

Similarly the other tables described above.
Once you've simplified the structure you can then think about how to handle orders...which will need a separate table

[sully944]

Thank you! I have been trying to figure this out in a vacuum so I'm really glad to be a part of a forum! I can now see I'm over normalising now that the word has been spoken . I'm straightening that out now.

Welcome to the forum
.
I think you can dramatically simplify this as I think you are 'over normalising'.
There are 9 tables with a PK field and one other field.
There are another 2 tables with a PK field ONLY.
It's unlikely you need to store these separately.
If so, scrap most or all of those tables

For example tblLicenseID - enter the value using a form and save in tblVehicleInfo.
Suggest you remove the underscore.

Use a query if you need to get a list of licence plate values.

Similarly the other tables described above.
Once you've simplified the structure you can then think about how to handle orders...which will need a separate table

[isladogs]

You're welcome.
The good news is that by trying to normalise your db from the start, its easy to put right
Many Access newbies miss that point completely and treat Access like a spreadsheet on steroids which it definitely isn't - that approach is MUCH harder to put right

[sully944]

Ok so this is a little more normally normalised. Is it a correct assumption that injecting the recstatus which will change at the least 5 times in service process be in a separate order fulfilment table or is that doable in the tblserviceorder logically?

[isladogs]

Sorry I don't understand what you mean.

Also, can you please expand each table to show all fields - at least one - tblEvents - still looks unnecessary & there may be more
Also I don't understand why there are several fields showing a - sign and an indented field name.
I've never seen that before and am unclear what that means
Lookup field in a table perhaps? If so, not a good idea either

[ssanfu]

Echoing ridders52,

Here are some suggestions:
Use only letters and numbers (exception is the underscore) for object names.
Do not use spaces, punctuation or special characters in object names.
Do not use look up FIELDS, multi-value fields or calculated fields in tables.
Do not begin object names with a number.


Maybe you would post your dB.... doesn't need any records. Do a "Compact and Repair", then Zip it.