Done that already and ran under administrative account, no dice. The error message doesn't make sense in the first place. Anyway for me this case is closed.
Cetin

>If it works in File based but not in COM then almost certainly the problem is one of permissions. Make sure the COM server is configured to run in an execution context that allows for ADO.NET COM access and has access to the folder where the data is stored. The default is the launching user which is NETWORK SERVICE which doesn't have rights to read/write files.
>
>Use DCOMCNFG to set the proper impersonation on the COM server that has the same security context you are using when running logged on in File Mode.
>
>+++ Rick ---
>
>>>Cetin,
>>>
>>>Web Connection does nothing to change the base operation of Visual FoxPro, so whatever the error is, it's not likely to be caused by Web Connection per se...
>>>
>>>Are you running in COM mode? File Mode? It's possible that VFP under COM operation behaves differently when dealing with ADO recordsets???
>>>
>>>A type conversion usually means that the wrong cursor is open - maybe a work area is switched the wrong way when the import occurs.
>>>
>>>+++ Rick ---
>>>
>>
>>OK after some tweaking it worked with File based messaging. I am not happy with it but I can live with it:) Thanks.
>>Cetin