I want to create a assembly of records from multiple tables that can be stored and used anytime by pressing a button. Creating a button and executing the script is not the problem. I'm thinking I need to export the records to folder for import as needed. The problem is not exporting the data and having the data come back in but for it be assigned to the new ID.

SIMPLIFIED SCENARIO: Table A is related to Table AA & AB.

I would create in TABLE A the title of the "Assembly". Records from AA & AB would be the assembly.

Any help or tips?

Your question is too abstract, using aa as well as bb's doesn't help at all. We need context and purpose, before answering at all. Further more doesn't it seem proper structured to have data of near similar form scattered over several tables often will sets however be solved via recursive structures:

http://www.jonathanstark.com/recursive_data_structures.php

--sd

Apparently my simplification of my problem was not quite as stupid as it appears. When I got to page 27 of your article I realized you had an answer. I however was looking at it at in different perspective. I'd still like to pursue the importing assemblies idea.

I'm not speaking of stupidity here, but merely the thought that a concise and to the point description of a problems context and purpose eliminates a lot of guesswork that an diffuse abstraction never can reach.

Think here of what a light pole and statistics have in common, they're convenient to lean against but gives bad light ... as a Storm P. "fly" says!

Since you now luckily have narrowed down the scope a tad by saying it has similarities to the many2many recursion, am I able to guide you to a template made by a great mind, who has what I guess is some kind of ignorance to theory, used his ingenuity instead to come up with a filemaker near implementation of such problems.

http://www.dwdataconcepts.com/dl/tw/compinv2.ZIP

--sd

Edited October 7, 200817 yr by Guest