Saving data back into a table from a form

[pbaldy]

Did we miss post 14?

[skyview chick]

The problem lies in the link between the main tables "Clients" and "Installation" The main form being "Clients" where we add new clients and info about their installation. I know this isn't totally ideal especially if one address has more then one installation, but it's how it's been set up so far
The "Installation" Forms pull information based on the installer assigned so that the installer can't see another installers notes or customers. They will log into a portal and add their installation information from the actual customers home.

[skyview chick]

Sorry my computer didn't update to see post #14

[pbaldy]

For starters, the query that form is bound to is joined on the wrong fields (Client ID to Installation ID). Second, the typical way to display this would be a form bound to the clients table with a subform bound to the installations table. Master/Child links keep them in sync with each other (if you use the subform wizard to add the subform, it will ask about the linking fields and set that up for you). That would also let you view multiple installations for each client.

Trust me, you don't want those forms and tables that are installer specific. You don't want to maintain 20 forms and tables, and you don't want to add new ones when you get a new installer. You have installer be a field in the installations table, and it's a simple matter to open a form restricted to a specific installer. The concept is called normalization:

Fundamentals of Relational Database Design -- r937.com

[skyview chick]

Ok - I'll work on the form/subform. I'm not sure I know what you mean by opening a form restricted to a specific installer - because it would have to restrict the client information that they see as well as restrict what clients and installations they see.... I'm not trying to duplicate data, just restrict people to only see certain data & fields based on criteria.

[pbaldy]

You can base forms on queries with a criteria for installer or use this type of thing:

BaldyWeb wherecondition

You definitely don't want to maintain all those forms. You get them all set up nicely, then decide on some new field or feature, and you have to modify 20 forms. I'm lazy, so I'm just modifying 1.

[skyview chick]

Well that would be MUCH better if I only had one form to maintain. I'd have to have them log into the form though and then have the data shown based on their login I guess? I'll read through the info and see if I can figure it out. Thank you SO much for your help!!!!!

[pbaldy]

Sure; with your method you also had to know who was logged in to know which form to open.