library members not exporting

4 posts / 0 new
Last post

We're having a problem where constructions are not exporting properly onto other machines.  Typically they're all missing the inside and outside surface resistances, although other layers are sometimes missing as well.  This happens with archive files or when you just export a library and import it on another machine.  Is anyone else aware of this problem?  Any potential solutions?

ajuran's picture
Offline
Joined: 2011-05-12
Reputation: 0

Ouch -

I actually had this problem, now that you mention it. I had to add the layer - which was blank, so it was easy. But, TRACE doesn't let you leave a layer blank like that, so it has to be an import problem. FYI - mine was only missing one layer - the interior resistance.

I can't think of a solution, but I will look into it. It is probably a bug in the library, that will require an update from CDS.

Think of the library db like a spreadsheet. When a Trace 700 update come out that adds more features, the library essentially gets more columns, and I think the columns may not be "lining up" for certain import/export processes. As such, it's hard coded, so a user can't do much.

Or perhaps you are exporting from one version and importing to another. I am not sure which version the files I am working on were created in, though I know it is pretty current.

Bob F's picture
Offline
eQUEST UserLEED EA Credit 1 TrainingTRACE 700 User
Joined: 2010-06-30
Reputation: 18

Called CDS... their initial idea didn't work so I'm sending them my entire library and some other stuff.  Will post what I find out!

It does seem to always be materials from their 90.1 library that are missing.

ajuran's picture
Offline
Joined: 2011-05-12
Reputation: 0

So after going back and forth with CDS for several weeks it appears that this only occurs when you use 90.1 material library members as part of a custom construction.  My understanding is that originally these materials were custom, but are now standard.  So, if the one machine has them marked as standard, but the other machine has them marked as custom it gets confused when you import a new archive file.  The easy answer is to not use these materials, or copy and rename them if you plan to.

ajuran's picture
Offline
Joined: 2011-05-12
Reputation: 0