John,

I don't know if this is any help in your situation, but we create a service account (just a plain NT user with a non-expiring password) and set the MTS package identity to that account. The account can belong to an NT group and share wide permissions or can be granted restrictive permissions at the directory level. All of my work with MTS has been in the middle tier between "standard" VFP apps and SQL Server, I haven't faced the ASP challenge yet.

Bob

>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.