Gavin wrote:

>Jim after somebody:
>> > > Examine the page (or watch the traffic on a network analyzer)
>> > > to determine what data is required, then use an appropriate
>> > > development or scripting environment to do explicit HTTP POSTs
>> > > to the URL to upload the data.
>>
>> Will this idea work with scrollable pick lists and such?
>
>I sort of suspect that anyone stupid enough to require their vendors to
>hand-key all this data into a web browser are also likely to have highly
>"dynamic" web applications, so the hazard is that as soon as you figure out
>how to automate this, they will change their web application in some subtle
>way so that either your automation breaks, or silently starts creating
>incorrect / corrupt information.

That's true, but there's a good way around it. This is a situation
tailor-made for [plug your ears, Gavin] XML. I presume that it's easy to
generate an XML encapsulation of the data at your end (which it is if all
the information is computer-generated), and since the customer obviously
has some clever (or rather, Microsoft-immersed) web programmers at their
end, they can just as easily decode it. You can then offer automated
delivery of quality data to all your customers.

-- Bruce


--------------------------------------------------------------------------
Bruce Toback    Tel: (602) 996-8601| My candle burns at both ends;
OPT, Inc.            (800) 858-4507| It will not last the night;
11801 N. Tatum Blvd. Ste. 142      | But ah, my foes, and oh, my friends -
Phoenix AZ 85028                   | It gives a lovely light.
btoback AT optc.com                |     -- Edna St. Vincent Millay
Mail sent to [log in to unmask] will be inspected for a
fee of US$250. Mailing to said address constitutes agreement to
pay, including collection costs.