I hope this is the correct category, my apologizes if not!

I have created a popup window to use as a data entry dialog. I would like to be able to create a new record in two different tables to ensure that the primary ID of both tables and a field called "name" are the same in both tables.

Can this be done?

More information if needed...

The two tables contain settings for printer profiles. We have different paper types that can go on one of two different printers, the paper needs to have a profile but that profile may be a little different depending on which machine it goes on. I would like to keep table called "paperTypes" which has a relationship to two different tables called "deviceA" & "deviceB". I would like the popup which I have already created, submit just a name to a new record in both tables, which should also automatically create a serial number in each table. I hope to keep the "serial number" & "name" fields in both device tables the same.

I hope this make sense.

I am avoiding having one table with a ton of fields prefaced with...

devA_setting1

devA_setting2

devA_setting3

etc.

devB_setting1

devB_setting2

devB_setting3

etc.

Thanks a ton, May the Lord bless you unto salvation through faith in the work of Jesus on the cross!

I would like to keep table called "paperTypes" which has a relationship to two different tables called "deviceA" & "deviceB".

Doesn't sound like a good way to go about this. I believe you should have one table for PaperTypes, and another table for the Settings - so that as long as you have 2 devices, there will be 2 related records in the Settings table for each paper type.

Strictly speaking, you should have 3 tables (at least):

PaperTypes -< Settings >- Devices

If you allow the relationship to create records in the Settings table, a new setting will be automatically created for you when you enter data into the portal.

I am avoiding having one table with a ton of fields prefaced with...

devA_setting1

devA_setting2

devA_setting3

etc.

devB_setting1

devB_setting2

devB_setting3

etc.

You should also avoid having a ton of numbered fields like:

setting1

setting2

setting3

May the Lord bless you unto salvation through faith in the work of Jesus on the cross!

No offense, but I think this may be rather inappropriate in a professional forum.

Only the Sith deal in absolutes, Comment. :D

Edited June 7, 201114 yr by Vaughan
added the smiley to indicate humour

Beg pardon?

Consultant, Thanks. I will have to try to create the structure you recommend, I am not sure if that will keep my data quite the way I was hoping but I am sure several ways will get the job done.

Also I would not have numbered fields like that in reality I just did not want to type all the names of each parameter. Thanks for the heads up though, that would make for a real headache!

Is there any chance you could elaborate on your statement

If you allow the relationship to create records in the Settings table, a new setting will be automatically created for you when you enter data into the portal.

Thanks a ton, and again may the Lord Jesus bless you sincerely!

Is there any chance you could elaborate on your statement

See if this helps (point 4, first row):

http://www.filemaker.com/11help/html/relational.11.13.html#1028508

Are you really using version 8.5?

and again ...

... in vain.

Yes that helped. Yes I am running 8.5.

Part of what I am trying to do is keep a matching record(profile), one for each machine. In other words I am hoping to click a button to add a profile and have it actually add two entries, one in a table for the DeviceA and one for DeviceB. I do not want to have a profile that only has a record for just one machine. When a profile is created it is to be created for both machines which will both have slightly different variables. If I understand your structure I would have the profiles for DeviceA and DeviceB on different records in the same table. However this would leave the possibility of creating a profile on DeviceA and not creating a Matching record for DeviceB. Also I was thinking I would like to keep the records for each device in two tables to keep the records neat and related only to the device it is for. I will want to output data of all profiles and be able to run calculation per device which I guess I could handle based on specific queries to the table based on a device field. I just thought it would be easier to keep it clean.

Am I understanding your structure correctly? Am I looking at something wrong?

I do not want to have a profile that only has a record for just one machine.

Is it any better to have a profile that has an empty record for the other machine? Creating the record automatically can be scripted - but what purpose does it accomplish, if no data is entered into it?

My suggestion is for a record to be created automatically when you have the data for it. If you want to make sure users enter profile data for both machines, use a validation in the PaperTypes table.

I was thinking I would like to keep the records for each device in two tables to keep the records neat and related only to the device it is for.

Assuming the settings parameters are the same for both devices, there is nothing "neat" about this. It's just maintaining two identical tables instead of one.

Each record should be related only to the device it is for - that's why you need a DeviceID field in the Settings table.

added the smiley to indicate humour

I understood it was meant as humor, but I still don't get it. Is this some kind of reference to a popular cult... woops.