I have run an old (1996) Windows program that accesses DBF files. If I run with an old copy of the database it works fine. But if I run with my current copy of the database, I get the GP Fault when I take a certain action.
I conclude from the above that there's something in the current database that the program does not like, but when I take the action I just get the name of the DLL that caused the fault, and a hex location (0001:0F7F).
Is there any way, any tool, any process that would let me see what the program is trying to do when it bombs? This might give me insight into fixing the database. For instance, if the process before the bomb is joining of two tables, then I'd know which two tables to clean-up.
