Rich,

I later recalled that my user was also getting c0..5 when running my update.exe, which just copies a few files with no REGFN() in use. Therefore, I know it isn't causing the problem. However, Despite David's experience I've still been getting sporadic invalid API call errors when running my code in development mode, and I know the REGFN() is where the problem occurs. Who knows how this translates to production mode, so I am going to switch to calling the API directly. Of course, if I WASN'T getting any errors I probably wouldn't even think about changing existing uses of REGFN(). If it ain't broke... Thought you might benefit a little from my experience, Good Luck.

Marcus.

>>You don't need REGFN() to work with the windows API any longer. You can DECLARE the function and call it directly:
>
>David,
>
>I was curious about this when I saw Marcus' original post. I know about the DECLARE command's existence, but I'm wondering: if you try to use FoxTools RegFn/CallFn now, instead of DECLARING etc., should it cause errors (C5 or otherwise)? Has it become bad to use RegFn?
>
>Just curious,
>Rich.