Richard - can I suggest a couple of additions to your users 'wish list' for the next big update:-

1) Comment field [say 200 chars long] for each node so users can make notes etc to help checking, data verification, record assumptions etc.

2) Some sort of programming interface [like excel VBA or AutoCad AutoLISP] so users can write macros to do manual calcs within Caesar, based on the raw data Caesar produces

3) [this ties in (1) & (2)] Auxiliary user defined datafields - say 3 x text & 3 x number formats

If you're not sure what I'm getting at with (2) & (3) let me know and I'll post some psuedo-code showing what I'm thinking of

1) Yes this would be a good thing. 200 chars would be quite a lot of data space to allocate and manage. Assuming we did this (it won't be in 5.10), what are your ideas on how this information would be displayed or printed (at the output level)? Would you want this available in the graphics?

2) Actually someone (outside COADE) is already working on this.

3) I'd like to see your ideas here. Adding fields is one thing, making the data available for use outside of CAESAR II is another.

Item 1: Good idea. Facility is already partially included as part of stress ISO. Printing should be as separate report giving node number and also preferably as a box on stress ISO (as it is now). Prefereably info should not be lost on SaveAS or there needs to be a system to reconnect it to the saved model. This loss of data on SaveAs is a real problem on stress ISO annotations. Large models/models with a lot of info have to be split up to be able to run stress ISO. ISOGEN has limits what it can absorp in one go. 8000 lines in PCF file is the max.

I am using the "node name"-function starting with release 5.00 for vessel nozzles and support numbering.
Please change the properties of the "node name"-function by expanding to a higher character number (currently limited to 10 characters) and/or deleting the unique property of the "node name"-field. At the moment I get the warning message number 162E in cases of duplicates.
Thanks and Regards

"At the moment I get the warning message number 162E in cases of duplicates."

I disagree with your desire to eleiminate this.... if you use the same name for two sperate nodes which node do you really want data from Name1 or Name1?

Their should be a fatal error rather than a warning for duplicate names.

"(currently limited to 10 characters)" This is all that wwill fit in some of the current report formats.

Let me add some fact. It makes sense to give information to people not familar with pipe stress analysis reports details about support name/location and support function requirement in accordance to our company-standards.
That is in summary:
area-no. (3char),
support-no. (4char),
support-function (2-4char) and may be separators.
Using that complete information is not possible because of the limitation to 10 char. Not using the area-information somtimes produces duplicates.
In my opinion the NODE number is the only unique information of a CAESAR II system.

best regards