1) Actually it is exported properly. The CAESAR II input file is actually a difference file. So for example, the diameter is actually stored only on those elements where you typed in a numeric value. (You can see this if you look at the Element List, the values in <font color="#ff0000">red</font> are the values you typed in. The values in gray, are the ones CAESAR II duplicated for you.)
The ODBC export simply sends out the raw data from the file, so the zero is in fact a correct reflection of what is in the input file.
2) I just verified the "bend_pointer" data - it is correct. One thing you have to be aware of is that the bend pointers are assigned increasing numerical values (1, 2, 3, etc), but are assigned to the elements in the order in which you define the bends. So, if you defined the bends as you built the model, walking down the pipe, the bend_pointers should be in "counting" order in the Element_Table. However, if you forgot one, or sometime later went back to the system and added an expansion loop, the bend_pointer values would not necessarily be in numerical order. This doesn't really matter though. If element #50 has a bend_pointer value of 11, then element #50 is assigned the 11th bend, and the bend data is in the 11th slot in the bend array.
There is nothing wrong here. You can get a better understanding of the data structure if you review the section in the Technical Reference Guide on the "Neutral File Interface".
_________________________
Regards,
Richard Ay - Consultant