More info:
I have 3 geometric networks: Storm, Water, and Sewer. The storm network is the one previously mentioned giving me problems when validating the swPipe feature class. I just performed the same validation test with a water pipe (waPipe) feature and sewer pipe (wwPipe) feature in my other 2 respective geometric networks and the validation worked fine!
The same domain is used for each of my 3 feature classes: Domain name: �??d_PipeSize�?�, Field Type = Float, and Domain Type = Coded Value. This domain contains whole numbers and fractional numbers and why we chose the type = Float
The attribute field type for swPipe FC holding the d_PipeSize domain is Short Integer.
The attribute field type for the waPipe and wwPipe FCs holding the d_PipeSize domain is Double.
My current thought about this problem is that the field types between the attribute field and the domain conflict at some level. swPipe > d_PipeSize attribute field is Short Integer, but our d_PipeSize domain is Float. We need the domain to be Float since we have decimal values in the domain (1.5, 0.75, 1.25). I think that the validate command sees a problem between the Short Integer attribute field, (Short Integer only allows whole numbers) and the domain of Float which contains fractional values.
I however don�??t know why our current 9.3.1 SDE geometric network allows the validate to work properly and when I create a new geometric network in our version 10 SDE database the validate works fine on my storm features�?�maybe creating a new geometric network forces certain references?
Do you think this is at all on the right track?
Thanks,
-Nate