【转帖】importing multiple sat files into one assembly

yang686526

importing multiple sat files into one assembly
we have to put our solidworks models into the model of our client. so we need to open their model in solidworks.
the best way to import their model is if they cut their model up into 5 different groups of elements and export them as as 5 seperate sat files (memory-reasons!).
when we import these files in solidworks, all the elements are named imported## when saved as an assembly. our problems begin when we put together the different converted assemblies in one main-assembly; several filenames are identical, resulting in dissappearing elements because they become replaced by elements that are named the same.
could someone give tips on how to avoid this problem?
maybe there is a way to alter the names that the imported parts are being given by solidworks?
forgot to mention that we are using sw2007...
can they give you parasolid or step files instead of sat?
separately open each of their sat files, save it as a part, then assembly the newly created parts.

thanx cor,
i know of the advantages of step and parasolid, but at the moment that is not an option.
we can't save as a part, because importing a sat file creates an assembly with multiple parts in it. not the name of the assembly is the problem, but the names that are given to all the different parts. (?? or am i missing the point)

an assy can be saved as a part. the assy parts become bodies in a multi-body part. individual body names become irrelevant.

thank you very much for your help cor, we are going to try that immediately.
what application is your client's models from?
chris
solidworks/pdmworks 08 3.1
autocad 08
if i am correct they use cadmatic (??)
i know they can export to step, but...
the first files were in step, sw crashed on them unfortunately. next thing we tried was sat, but that only worked after dividing the model up in several smaller files.
it took them quite a lot of work to arrange it all, last time i talked to them i could feel their growing discontent through the phone   i did not dare to ask to repeat the whole procedure to give us the subassemblies in step format.
luckily the cor-tips worked, so we can proceed now.

insert --> feature --> imported