>You might put a messagebox or something right before the set step on just to be sure the code is actually executing (you might also turn off the error handler at that point too, just in case some error is occurring and your error handler is causing this strange behavior).

Yep, I've got a WAIT WINDOW "BEFORE SET STEP ON" right before it.
Error handler is working because the error gets logged properly.

Another clue: SUSPEND give "FEATURE NOT AVAILABLE ERROR"

I'm starting to think that it relates to the way I handle DLLs. I copy everything I need to a directory on the C: drive and then switch execution to the main program in that directory.

When I execute the my program in the development area I don't see the problem. I also have DLLs for Version 6 in this directory. I'm suspecting that there is some confusion or overlap between the 6 and 7 DLLs.

These are the DLLs in the local directory:

06/09/98  01:00a                 6,656 foxhhelpps.dll
03/12/01  05:55a               303,104 msvcr70.dll
03/08/01  10:31a             1,110,528 msxml3.dll
03/08/01  10:30a                24,064 msxml3a.dll
03/08/01  10:30a                43,520 msxml3r.dll
04/22/02  01:14p             3,373,328 VFP6R.DLL
11/21/01  12:27p               876,032 vfp6renu.dll
06/14/01  05:31p             3,416,064 vfp7r.dll
06/14/01  04:08p               901,120 vfp7renu.dll
06/14/01  05:32p             3,063,808 vfp7t.dll
07/26/00  02:00p               977,680 vfpodbc.dll
08/20/96  01:00a               174,592 vfpole50.dll

Peter