Perry,

It was a false alarm.

I got caught up in the "fast" computer problem that surfaced at the same time.

Had forgotten that I did a fairly major upgrade a couple years ago and put the new version in a new directory. Because users were putting other personal files in the old master directory, I didn't delete all the files in that directory. There was only one person using these particular reports and she still had the old directory on her old computer. Others had been deleted long ago.

Anyway when they loaded the new computer the old master directory wasn't copied. The file with the "rp5" extension was missing and even when it was put into the new directory, it was still pointing to the old.

By the way, the problem you mentioned...I had the same problem with fp"DOS"2.5. That's one of the main reasons I'm not using R&R anymore. As soon as people started upgrading to win3.1 and win95 they started having that problem with their reports. R&R told me the same thing and I deleted drivers from Config.sys and Autoexec.bat. Got conventional memory into the high 500s and it still wouldn't run.

Hope this makes sense...anyway I got it working.

Thanks for your input.

Dale

>Dale,
>
>I had a similar problem from an app I inherited a couple years ago. I called R&R and they said it was a problem with not enough conventional memory available to run R&R thru Foxpro.
>
>There was a ton of reports, but I ended up taking the most used ones and rewriting them in Foxpros report writer. We set up and old workstation to run the old version of the s/w for the little used reports.
>
>You might need to get creative in solution also.
>
>PF