>>>I have a VFP COM component running in MTS on a remote server. The component functions correctly with one exception: I can't make it write a disk file on my client using the RecordSet.Save method.
>>>
>>>I can change the path in the DLL to point to a directory on the server and it writes the file correctly. I can run the DLL locally on the client and it will write a file in a local directory. When I run it from MTS it doesn't write a file anywhere (that I can find!) and it gives no error messages. I know the rest of the component is funtioning correctly because I see the proper results in its properties. I can write the recordset into an array and passed it to the client as a property of the object, but I know I should be able to persist the recordset on the client hard disk.
>>>
>>>I have what I believe to be the required NT user accounts and MTS identities set up on the server where MTS is running and SQL Server accounts set up on another remote server where the data is stored. I must be overlooking something.
>>>
>>>Any ideas? Thanks
>>
>>I want to make sure I understand what you are trying to do. You have an MTS component that runs on the server. You have code in the component that should write a text file to the user's workstation. I don't think this is possible. The NT Server/MTS would have to be given the proper rights for each workstation.
>
>Craig,
>
>I have created a share on the client with Full Control permission given to Everyone. The code in the component is something like this:
>
> loRS.Save('\\\\')
>
>It's not a text file, it's a copy of the recordset in the default Advanced Data Tablegram format used by ADO. The MTS component is running under the identity of local admininistrator on the server. All machines in question are in the same domain.
>
>Bob, I will keep you informed as to my progress. The purpose of the system is to get the serial number from a product via bar code scanner, ripple through our convoluted configuration management system, and ultimately return the test spec for that version, model, and option of the product. Thanks for the response.

Looks like the UT server didn't like my use of greater than and less than in the sample path name. It should read:

loRS.Save('\\clientname\sharename\filename')

Bob Tracy

Never engage in a battle of wits if you're only half armed.