Hi Barbara,

>Check your Task Manager to see if the DLL is left open as a process when you run your macro.

The doesn't seem to appear in task manager at all [unless it is assigned an odd name].

>Maybe you could try a VFP Release command? Sorry I didn't have a VFP DLL to try out, but I could repeat the 'nonrelease' of the "Set oTest = Nothing" command.

I'm not sure what you mean by this - what do I do in Excel ?

>
>I also found that I had to issue the "Quit" command before setting the object to "Nothing" (got an error otherwise) which confirmed your finding that the value WAS changed.

I'm considering creating a com exe instead of a dll - I've created com exe's in the past and haven't seen this problem. I'd much prefer to have the dll work, though.

We should be able to test it on the web server today, so I'll tell you how I get on.

Best.

Matt.