I'm looking for the easiest way to copy a relationship graph from one file to another.

Thanks

Cloning ?

Yes, I have a clone that I use on another computer so I can view the relationship links from the other file, but still have to manually link them in the new file. I'm still wondering if there is a way to copy those links from one file to another.

Is there another way I could be using the clone?

Thanks

What's in your new file that isn't in the clone (other than data, that can be imported)?

I purchased some code which is designed around a "Contacts" table and I am merging it with extensive work already done for a client and their contacts table. There are probably around 150 Table Occurance branches which branch off the clients Contact table and 50 currently branching off the new code. Both need to be preserved. I am merging the client solution into the purchased code.

Thanks

I don't know of a way to do this in Filemaker. Perhaps you could use a third-party tool like FmPro Migrator (I haven't tried it myself), or just use both files in the solution (after changing the file references in one of them).

Thanks comment,

I'm more than half way there now so I think I'll just persist. I have learned allot in the process though so if anyone out there is going through the same thing, I'd be happy to share.

One real help was in creating a valuelist of table occurences and using that list to build the new table occurences.

I stayed away from separate files in this cases for a range of reasons from loss of flexibility inherent in the built in nested table functionality that I didn't have in other multi-file solutions I worked on in the past, to fear having to adjust too many scripts, value lists, calculations, etc.

I did have another post inquiring about the use of XML data and whether or not that could be used (when imported), to build the relationship graph but I haven't had any answers yet and have to keep moving on this.

Thanks again

Alas, XML data, like any other import, is always imported into a single table at a time. It's a pity that FMI didn't extend their XML grammar to allow multiple tables in the same document - but it wouldn't help much in this case, unless the nature of the relationships were also included.