To All,

Several of our apps use a DLL written in C++ for the most crunch-intensive calculations.
We've been experiencing several wierdnesses with this DLL:

Wierdness 1) The first time I call the dll in my VFP6 code, it errors out with "API an exception".
I [ignore] through the rest of the VFP errors, rerun the query and the dll runs with no problems.

Wierdness 2) I renamed the DLL and retrieved an old version of the DLL from our version control system.
When I ran the old version, I got no errors... no suprise because the old one had worked perfectly.
Just for grins, I renamed the old DLL to something innocuous and then renamed the "new" file back to its operational name.
When I ran my code again, the "new" DLL ran fine... no problems. This is physically the same file... all I did was rename it. It was suggested that "old" the DLL was still in memory when I ran the "new" DLL, so I shut the box down and restarted... the "new" DLL still runs fine.

Wierdness 3) We're doing OS testing on the app with WIN 95, WIN 98 and WIN 2K.
On the Win 95 test machine, the "API exception" error occurs on the first run of the DLL.
On the Win 98 test machine, the "API exception" error occurs only after a report has been printed. While the problem
may be related to the print driver, I suspect the OLE call to Crystal Reports (ver 8.0.1) that we're doing to run
the reports.
The Win 2K test machine has no problems with the DLL.

TIA for any help.

Regards,
Thom C.