>> When I looked to see what version of UFT >> I have, it gave a choice of looking at the >> Microsoft Summary. That is where I saw >> the MSINF16H.EXT message.
Oh! That's different.That's an unrelated problem and nothing to worry about (insofar as data integrity).
>> The PNO error message appears just after >> I choose the UFT icon. At the top of the >> screen says Microsoft FoxPro. After that, >> I go into UFT. Therefore, I did not yet >> Save As using a different project name >> because the error message occurs before >> I get into UFT.
You're mistaken about that.Although the window says Microsoft FoxPro, you *are* running UFT at that point and the error *is* being triggered by something in your system or data that warrants concern.Copying the project is the first best strategy at this point.
>> You have been very willing to help. >> Are you part of the UFT tech staff?
No, I'm really a competitor but I don't go out of my way to identify my affiliation when offering to repair files because my offer doesn't come with any solicitation or strings attached.In this context, I'm just a researcher who is concerned about your potential loss of data and I happen know more about the UFT file structure than anyone else that you're likely to reach.
>> Where shall I send my disk(s)? There are >> 6 projects and some of them have 3 disks. >> Do you just want one project?
All six projects exhibit the same problem??In any event, I just need one.When we discover the problem, we'll apply the fix to the others, if appropriate.
You can send it to my e-mail address as reflected when you click on my name above ("Posted by").I'll acknowledge it if/when I receive it.
Feel free to send further correspondence on this issue to the same address so as to spare the others on this list.