>I have built a MTDLL VFP6 COM object that I'm calling from ASP, I've tested it and it works fine on my production server. However it has now been moved to it's own server on the server farm where they are very touchy about security!
>Whenever the COM object tries to write to tables it gets a '#111 Cannot Update the Cursor' error. The dbf's and dbc are not read only!
>
>I am assuming this is about permissions. The server guys do not want to allow W permission for obvious reasons, and I haven't allowed them on my server where IUSR_server has R & RX permissions.
>
>If you want to look at it (not) running then take a look at http://212.111.129.146/test_register.asp, the test_ prefix indicates that it will output the contents of oVFP.cError at the end of each script block.
>
>Can anyone help me? How can I give the DLL permission to write without giving it to the IUSR_ account? Why might there be such a difference between the production and server farm servers?
>
>Massive Thanks in Advance,
>
>John C Scott.

This IS definitely about permissions. If your COM server is compiled as a dll and is being called directly from your ASP, then it is using the _IUSR account. There is no way around giving it W rights if you are configured like this.

YOu have 2 alternatives- one, compile your COM server as an out-of-process exe, and use DCOMCNFG to have it impersonate an account that you can give rights to. The second alternative is to put your dll in an MTS package, and have that package impersonate an account you can give rights to.