So you need a mechanism on the server to kick off the Updategram? How does the XML file get back to the server?

I guess you could create a small program on the server that checks the location where the XML file will be and does the posting. A small VFP program with a timer would do the trick. Being on the server, you can control the environment and use ADO or the XML Parser to post the updategram. You also still use IPStuff to do the posting on the local server.

A simple way to test this is to 'run' the Updategrams by placing them in the XML virtual directly and simply accessing them with your browser. For example, if your file is call 'yourxml.xml' and is located in the virtual directory 'yourdata', you can just get in I.E. and specify the url http:\\localhost\yourdata\yourxml.xml and it will 'execute' and post the file. Again, the directory 'yourdata' must be define in the XML for SQL Server tool as being an XML directory and it must contain an XDR schema file. If the directory is set up this way, you'll get the results file back. If it isn't, you will just see the entire XML file like any other directory.

>Thanks once again for a detailed reply. I have a slightly different problem however. I have queried a SQL Server table converted to XML, sent it to the Client, updated it, brought it back to the server as an XMLUpdateGram and now while I am on the server I want to update the SQL Server Table with the XMLupdategram. ie I want a DLL on the server to be doing the update as it subsequently needs to do some computations on the server.