> I am reluctant to post the actual file
> because of customer confidentiality
I'd work with the source, then, and resolve the export / import problems. Ten years ago this type problem was common. It's the exception to the rule today and can usually be resolved, often by correcting modeling problems in the native source file or trying different export options or a different neutral translation protocol.
...
You could export and post relevent bounding surfaces, presumably, without giving up 'IP'. Having some specific geometry to examine might reveal a simple (i.e. sweeping in a new surface using one bounding curve as section, extending a bounding curve and creating a swept blend, etc.) fix.
As a matter of curiosity; your import log will contain a list of goemetry entities read and, possibly, errors encountered. Can you post the pertinent sections of that?
Have you tried importing with a different program? Look the same as the Pro/E read?
-Jeff Howard (wf2)
Sure it's true. I saw it on the internet.