>Scott, we haven't needed to set any rights on the VFP mtdll itself to call it from ASP. The virtual directory where the ASP script runs (that calls the vfp mtdll) has script/executables Execute permissions. The only time we need to add IUSR and IWAM for security is for Write access on the VFP data. This is on Win2k Server SP2. Make sure you have the latest SP since there are issues with SP1 and no service pack.

Ahhhhhh. I finally figured it out. I run a .BAT file to unregister and reregister my DLLs in the folder where the DLL is. I map drive W: to C:\Shared\Proj for a shortcut.

I ran the .BAT file while on W: drive, so it is registered under W:\Folder\prog.dll, not C:\Shared\Proj\Folder\prog.dll. This makes a big difference to IUSR account, since it knows nothing of the W: drive. However the interactive user would be able to launch it just fine because the W: drive is visible.

I reran my .BAT file from C: drive to re-register and it works now!