Antonio
Thanks for your help! Yes, the back-office app is the same. Basically, this is the current scenario:
My back-office app handles bookings of car rental reservations worldwide.
With your help, i created a web service that 'talks' to the company's web site ( http://www.ofran.com ) and inserts / modifies / cancels / checks status of reservations in the back-office. In fact, what i did is to create a 'web commands' table. The web services gets the xml parameter, parses it and adds a command into the 'web commands' table. In my back-office, i have an app that loops through this table, handles everything and sets status ( completed, error, etc... ). This works great, and extremely fast.
There is now a software company with over 500 installations that needs to enter bookings in more or less the same way. They told me their system knows to browse to a specific URL, then uses HTTP POST to send the XML parameter, then retrieves the answer ( also an xml string ).
So, your idea to create an ASP that receives the POST, 'translates' their XML string to the one used by the web service and creates the SOAP request is excellent, that will do. I only don't know how to achieve this ( i can barely write it :-)) )
By the way, if you need a good car rental deal anywhere on earth, send me an email ( that's the least i can do for all your help ).

Best regards,
Jaime

>If the back-office vfp application is the same in both situations, you could try to create an ASP that receives the POST, creates a SOAP request, calls your web service, returns the result in whatever format the caller is expecting. Does this make sense?