Level Extreme platform
Subscription
Corporate profile
Products & Services
Support
Legal
Français
R&R Report Writer will not run from FPW2.6 app. and Win9
Message
From
08/01/1999 12:36:29
 
 
To
07/01/1999 14:23:03
General information
Forum:
Visual FoxPro
Category:
FoxPro 2.x
Miscellaneous
Thread ID:
00173568
Message ID:
00174086
Views:
32
Dale,

Not that you mention it, it was FP DOS that was the problem. I screwed around with that stuff for weeks trying all kinds of possibilities to get it to work. No success at all. The worst part, I thought, was that my bosses wouldn't let me do any rewriting at all so the poor users were screwed.

When I started dealing with the dept. They were running the app in FP Dos 2.0. They were having to boot into DOS to run the app, or boot to windows to do anything else. I didn't have that much experience with R&R, but I did know that FP Dos 2.5 would run thru windows and run much faster than 2.0. I really felt sorry for the users in this case.

>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

(On an infant's shirt): Already smarter than Bush
Previous
Reply
Map
View

Click here to load this message in the networking platform