We have recently migrated our 16 bit finance application Pegasus Opera) from a dedicated Netware server to an NT server.  The application runs in Microsoft Foxpro for Windows ver 2.6a.  Since migration, we have been having the following error message -"Microsoft Foxpro - Unable to process error" - OK.  This hangs the application and you can only exit the application by rebooting the system.  This occurs at random - sometimes whilst trying to load the application and sometimes whilst working within the application.  This problem only occurs on Windows 98 machines, no problem with Windows 95 machines.  Moreover, we never had any problems running in Netware on both machines. Pegasus Opera Support do not seem to have a solution.  We thought it might be a 'divide by zero' problem, but trying to patch foxw2600.esl was unsuccessful.

Can anybody help???

We had the same problem when we move main application from Novell 4.x to NT4, the final fix was to do the following to every table.   Difference between you and me is we had VFP5.0 tables not FPW2.6a

Use xxx.dbf exclu
delete tag all
use copy stru to temp
use temp
append from xxx.dbf
use temp exclu
copy to xxx.dbf
use xxx.dbf exclu
index on yyy tag zzz
......
Needless to say you better document your indexes first.   If you do decide to go this route, I have routines that collect index index information and stores it in a database and routines that will do the above..  This is a drastic last ditch effort so weight the options first.


David W. Grewe
Dave@internationalbid.com
ICQ VFP ActiveList #46145644