Your problem really is that a specialist is NOT a subform of the specialty.
What you really have is specialties, and specialists, two completely independent tables, and a junction table specialty-suppliers identifying the services that the specialists provide.
So given your form, selecting a...
@CraigBaker
I think the real problem is that you are most likely out of your depth. If you weren't you would know how to do this. The best thing would be to spend a few thousand (or hopefully less) getting conceptual help on what is feasible and practical, and then deciding whether your...
You might have a corrupt memo field in a record somewhere, often visible as "Chinese" characters.
If you can find the bad record you might be able to copy the table into a new table in parts, ignoring the correct record. If it's linked in relationships, you might have to delete the...
The "search key" message sounds like a corruption.
Copy your database first, then try a compact and repair. It's not exceeded 2Gb has it? That would result in an error of some sort. You might need to create a new database, and import everything into it. (If you can). Be careful as you may lose...
Yes, but employees, cafeteria, enrolments is different to grandparents, parents, children. The first is a junction table to deal with many to many. The second is 1 to many rather than many to many.
But a system describing an allocation of two unrelated tables via a junction table, is not the same as a structure modelling three generations of a family.
To be honest I didn't understand the significance of the 3 record types, employees, enrolments and cafeterias.
I would not have thought you would map a grandfather to grandson relationship. All you need is a child (son) to father relationship. You don't need separate tables for these relations. All you need is a single table of all people, and to map the relationships of child to father (and child to...
Well it was a curious request. It sounded like "show me the look and feel of a sample access database".
If the requirement is just to demonstrate that an access app can look ok, then the suggestion to look at northwind might well be sensible.
If you want a data entry form, where you have clerks entering batches of new records, with no need to see records that have already been entered, then you want a data entry form..
If you are entering stock taking records it may be convenient to use data entry mode.
If you want to review all...
It probably fails to work as you would like because of the behaviour of a data entry firm. A Data entry form just allows you to enter new records in this session, and not see pre existing records, so I expect showallrecords just shows the new ones in the current session. .
With a module you call a procedure inside the module, so the module just can't be named the same as one of its procedures.
With a class module, the whole thing is a complete unit, and you instantiate an object of that type. The procedures and functions within the class module are methods of...