A problem to big to report (?)

I have reluctantly employed Creo 3.0 M020 in a production environment.

I now have a significant investment in effort and this project is moving forward this way.

Okay, that's the stage... and I am certain my issues are not only Creo 3.0 related.

As many of you know, I have gotten pretty good at submitting concise support cases...

but this one is befuddling me.

If you regularly create 3D curves using intersect, and regularly use datum references (the Datum Reference feature selecting curve chains).

As you might have guessed, I am in a spider nest of wires. See if any of this sounds familiar:

1. I create the intersect feature of 2 planar sketches. Nothing magic here; often you get a lot of extra intersects that are not continuous but valid.

2. You create a datum curve reference by selecting valid segments of the intersect feature... continuous of course.

3. The direction arrow are all aligned when I exit the reference feature creation.

4. When I try to locate a point along the datum reference, it fails to use the along value.

5. You edit feature the Datum Reference and you find the segment directions in all different direction then form when you left it.

6. Once redirecting all the segments, the point feature can be placed along the entire length (ratio 0-1).

7. You pattern the points; 1st point at ratio 0... and 10 more at 0.1 along the entire reference curve.

8. You then make a datum curve using the points; the 1st one is tangent to an axis, and the last leg is defined straight.

All good, right? Now you expect this to remain stable.

BUT NO!!! Every so often, you will get the 0 end of the Datum Reference to swap. This plays havoc with the tangent vs. straight segments of the datum curve because it too switches ends.

What did make it worse was when I also selected vertices to create the datum curve. These would get all tied up.

So, if you do this on a regular basis... What have you learned? Have you filed support cases?

Did you just give up and just live with it? Or do you just export a successful attempts and lock in?

I've dealt with this for over a week now so I am not just whining... there is a genuine reliability issue here. And not one that only happens every blue moon... it happens at every moon phase known to man.