V 2.03 and GEOID FILES and LOCALIZATION HANDLED DIFFERENTLY?

[tstrickland]

I have noticed with v2.03 if I load an old file that had a different named geoid, and the program can't find the file, that if I localize to a known point, all of the points that are stored are 90 feet too high, or the geoid separation.

This didn't happen in the other releases. You could localize and work without a geoid and still be close in elevations. Is something different in this one, or is this a bug? I have had it to happen on two jobs that came from a different data collector, and the data path was not the same.

What is going on? Anyone else had a similar experience with 2.03?
thanks,
terry