>>>>>Hi, all
>>>>>
>>>>>We are using "FoxFire 30" for VFP30 to create reports, and are getting Internal
>>>>>Consistance errors. This happens when a report is previewed, but not always.
>>>>>Sometimes after an error, if you copy the report to another name, and run the new copy it will run fine. This seems to be happening randomaly thruout the reports I have created.
>>>>>
>>>>>Is anybody out there is using "Foxfire" please let me know if you are experiencing the same problems and what workaround is there if any.
>>>>>
>>>>>Thanks
>>>>>
>>>>>Russ
>>>>
>>>>Russ,
>>>>
>>>>The only cause of random GPF-type instability errors in FF!, that I know of, was due to the use of a Windows API call when FF! loads to determine if Excel is registered on the system. Depending on whether or not Excel was found would determine if Excel output options were enabled or disabled. This only happened on a few systems, but in any event, we added a memory variable, m.pg_look4excel, to version 3.0+ that would allow developers to disable the Excel search, which is really not that essential, since the worse thing that happens to a user who trys to output to Excel, if they don't have Excel, is a message stating that output to Excel could not be completed.
>>>>
>>>>Therefore, I would upgrade to 3.0+, and set m.pg_look4excel to false. This can be done in FF!'s config file FFCONFIG.PRG, so no recompiliation of the FF! APP is necessary.
>>>>
>>>>Bill
>>>
>>>
>>>Thanks Bill i'll try that right now!!
>>>
>>>Russ
>>
>>We have been having some of the same errors. Inconsistant shutdowns and GPFs. We're using FoxFire! 3.0 and VFP 5.0. One other inconsistant error is a white message box, on exit from VFP, stating that DDEREG.exe has performed an illegal operation. Does upgrading to version 3.0+ and setting m.pg_look4excel to false address this also?
>>
>>Thanks!
>
>
>Yes, the DDEREG.exe is involved in the API call to determine if Excel exists. That error message on exit is the typical error that you'll get if your having the problem. Setting m.pg_look4excel to false will solve the problem, yet NOT prevent you from using the Excel output options.
>
>Bill

Hello All
Bill FYI
For the sake of this Thread, I thought I would pass on my findings on this particular subject. I did some debugging with the reports that were giving me and 'Inconsistence' Error. I selected and copied the SQL from the report and created a temp program with the offending SQL in the program. This SQL would run in VFP30b without a problem, however if I executed FoxFire and exited once the Request Manager activated. Sitting in the Command Window of VFP30b, and executed the Temp.prg with the SQL. It would then fail with an 'Inconsistence' Error. The problem in the SQL was a FoxFire calculated Data Item I had created that was contactenating "First_name, Middle, Last_name" via and 'IIF()' statement that was checking for an empty 'MIDDLE'. There were two of these in the SQL and would crash most of the time but not always. After replace all these calculated value's with a simpler calculation, all reports ran without any problems.

Russ