Your service could take your data as parameter(s) and store them in Access on the remote box. Take a look at Soap::Lite for Perl, there are some ASP examples there too.

--
hiseldl
"Act better than you feel" --inner prophet

ASP would be on the WinNT/IIS box. Perl CGI is being used on the Solaris/Apache box. Perl is not on the WinNT box.

I'll take a look at the SOAP stuff. Though, wouldn't I need a web-service running on the WinNT box, waiting to hear the remote SOAP call from the Solaris box?

wouldn't I need a web-service running on the WinNT box, waiting to hear the remote SOAP call from the Solaris box?
Yes, you will need an ASP/VB SOAP server, here is the example from the SoapLite website:

<%
    Response.ContentType = "text/xml"
    Response.Write(Server.CreateObject("SOAP.Lite") _
      .server("SOAP::Server") _ 
      .dispatch_to("/Your/Path/To/Deployed/Modules") _
      .handle(Request.BinaryRead(Request.TotalBytes)) _
    )
%>
[download]

Where your module would take your data and put it into Access.

--
hiseldl
"Act better than you feel"

MSDE 2000 is a free Microsoft baby brother to SQL 2000. It runs on the desktop but it limits the number of connections. I don’t know if it will run on as a server for Internet connections. But for local database applications under Windows, it can be valuable since it is royalty free and you can include it with your application.

Richard

There are three types of people in this world, those that can count and those that cannot. Anon