Multi-field Search

[ssanfu]

I looked at your db.
A minor thing, but having many tables with a field if "ID" can get confusing. I give a descriptive name to every field; "ServDescID" or "ServDescID_PK" gives you an idea what table the field is in just by the name, unlike "ID".

You have the relationship backwards between "Pigtail" and "ServiceDescription".

"ServiceDescription" is the one table and "Pigtail" is the many table.
One record in table "ServiceDescription" can have many records in table "Pigtail", one record in table "Pigtail" has one record in table "ServiceDescription".
The PK from table "ServiceDescription" should be saved in as a FK in table "Pigtail".



You have a potential problem between tables "Pigtail" and "WireType". There are entries in table "Pigtail" that are not in table "WireType".
I would have had an autonumber field as the PK. A text field will work, but if you decide to change "Tin" to "Only Tin", you will have to update two tables, then check the queries and forms to see if you hardcoded "Tin" into any column or control. I you use an autonumber field, it is just a matter of changing one entry in the table "WireType". I have an autonumber field is 99% of my tables (even if I don't use it).

[June7]

Steve, if Relational Integrity is on and Cascade Update is active, won't changing the PK from 'Tin' to 'Only Tin' reflect in the child records?

[ssanfu]

June, Yes, I agree.

IF Relational Integrity is set AND Cascade Update is set; but they are not in this case. I don't use Cascade Updates/Deletes very much (maybe I should use them more); however, I was told/read (a long time ago) to use Cascade Updates/Deletes sparingly.

I prefer to use autonumbers (if possible) to link tables; to me, I have more control. Control freak?? Yep!!

(I do use Relational Integrity!)

[June7]

I also don't rely on Cascade in my principle database (too many tables for one reason and Relational Integrity has limited applicability, mostly managed by code). My users have no need to modify PK and record deletion is allowed in only one situation and is only for a child table. However, have done some small dbs for others where I activated RI and Cascade features, one where absolutely no code (macro nor VBA) is implemented.

[bubba61]

Thanks Steve and June7, I really appreciate all of your help. Another question, if I decide to take this database online, does Access work well as an internet database? If so is it simple to do?

[June7]

Access alone cannot be web delivered. Need Sharepoint or web pages coded with something like ASP or ASP.Net or PHP that can interact with Access tables and maybe some other stuff I don't know about. Not simple.