Maybe someone can take the mystery out of this for me. When we changed over to WF5 the program file
now post like ######_xp##.. The _xp## is the post that the ncl code was processed through.
The mystery? PTC has no fix for this, post experts tell me they have never seen this yet in any other
clients with WF5. I know it is documented by PTC. We post out a .tap file that we run through a utility
program which opens the file in an editor (predator). This function no long opens the file.
Is there any way of preventing ProNC from posting the file with post extension?