Output individual records as PDF files

HI,

I'm back into it. To be clear, I have multiple tables with services and other item. For each table, I have to enter the client's name to record the data for each client. I was hoping to avoid this repetition. On that note, I am doing away with all the separate tables and creating a single table to handle all my data. I was under the impression that I should use multiple tables but without being able to assign a client to each table, I end up with orphaned records. 

And yes, I invested several more hours of my life reading tutorials. I created Primary Keys and then Foreign Keys but, according to you, I can't pull date from one table to the other unless I create form and subforms. I tried this too but I am unable to create a form from multiple tables. 

And so I ask again, what is the point of using multiple tables when you can use just one? Wouldn't that be easier?

And so I ask again, what is the point of using multiple tables when you can use just one?

In a word, 'integrity'.

A single non-normalized table inevitably includes significant redundancy in that each 'fact' is stated multiple times rather than only once.  This consequently leaves the table wide open to the risk of update anomalies.  Take the following simple model from my DatabaseBasics demo:

As you can see each contact's name is stored only once, as is each city, region, country, and employer name, i.e. at the relevant column position in a row in the relevant table.  Firstly simple errors resulting from inconsistent data entry or typos are ruled out, e.g.  I once found three separate versions of my own name as author of papers in my own field of work (environmental planning), K Sheridan, K W Sheridan, and K V Sheridan.  The first two are correct, but differ; the last is a typo.  As far as the database was concerned I was three separate people.  In a correctly designed database, with an Authors table, my name would only be entered once, so such inconsistencies cannot arise.

By enforcing referential integrity in the relationships between the tables it would only be possible for the region of Île-de-France to be in France for instance, whereas in a non-normalized database it could be shown to be in France in some rows, but incorrectly in Belgium say in others.

As regards data entry all data for the above model can be entered in a contacts form within which is a single employers subform:

For each table, I have to enter the client's name to record the data for each client. I was hoping to avoid this repetition.

but without being able to assign a client to each table, I end up with orphaned records. 

but, according to you, I can't pull date from one table to the other unless I create form and subforms.

As it always seems to be with you, you don't listen. You can't make something work, even with specific instructions and examples, so you assume it can't be done.

No you should NOT enter the clients name to assign a record to a client. You should ONLY enter the Client ID (the primary key of the client table) as a foreign key in each associated record. The main principle of a relational database is to reduce repetition.

There is no reason you can't assign a client to each related table. But you seem to think it should happen by magic. I've created hundreds of databases. It is SOP to use a subform to automatically enter the foreign key. Why you can't get it to work I can't fathom. 

Yes you cannot automate the assigning of a foreign key without using forms and subforms. Again, its SOP.