I posted a problem a little while back where my VBScript code was accessing a DBC through the VFPOLEDB driver. Sometimes it failed, sometimes it didn't.

It turned out the problem was that the OLEDB driver was installed under a local user account "scriptuser", but the user context the script was launching under was "dmz\scriptuser". When I logged onto the server locally, and the script was launched, it would run fine. When I was not logged onto the console, if the script was launched I would get "the driver may not be installed" error, which is what I think is a permissions issue, since if I manually ran the script from the local user account it was fine. I think I saw a permissions error for the "dmz\scriptuser" account.

To solve the problem, what I did was logged on locally as "dmz\scriptuser", installed VFPOLEDB driver again, and logged out. The script then launched fine.

It seems like there are some permissions tied to the driver's installation that made it initially break. I installed VFPOLEDB by creating a .MSI with InstallShield Express-VFP edition, and included the OLEDB driver and a .vbs to test it; I did not just copy the OLEDB .dll and register it.

What kind of permissions are needed for "universal" access to be available with the driver? I hope I don't have to re-install the driver for every out-of-process/service user account I have on every server....


Thanks.