Mark,

You have just raised an interesting point. I've been creating java applets
for database maintenance for a year or so using the following technique:
2 frames, 1(applet frame) for the applet, 1(data frame) for any data to be
transferred between the server and the applet when the applet is up and running
(initial data load occurs using PARAM tags). The 'data' frame uses the hidden
input tags for holding the data. When the frame returns, Javascript is used
to load the applet list boxes, etc. Initially, one of the motivations for
this approach was to prevent the form w/ the applet from being 'refreshed'(i.e.
want it to remain static while the data update occurs). During the research,
I talked to a few 'pure' Java guys and their only suggestion with respect
to going direct to the server to get the data was using IO streams and accessing
the data residing in an html file or text file. Got that to work,but it became
impractical relative to acquiring the data from an Access or SQL database.
Question is: is there a methodology and/or tools to access data residing
in Access or SQL Server directly(w/o transfer to a data/html file) from an
applet? Configuration of our server is NT 4.0, IIS 4.0(currently using ASP's
to handle the database access)?

Any response/reference would be appreciated.

Thanks again.

Dan
"MarkN" <java.@127.0.0.1> wrote:
>
>Just have the applet communicate with the server.
>
>"Dan" <java.@127.0.0.1> wrote:
>>
>>Using hidden input tags to transfer data to/from Java applet with ASP/ADO
>>load from
>>server. After initial load to browser, application periodically returns

>to
>>the server to refresh data in the applet list boxes. Volume of data on

the
>>intial load is approximately the same as on the refresh. Problem is the

>refresh
>>fails. After adjusting the amount of data refreshed, everything works(i.e.
>>5 rows returned works, but 20 do not). Because the initial load and refresh
>>use exactly the same ASP code, pretty much eliminated this being an ASP/ADO
>>database
>>access problem. Only thing left is a possible limit on the data the input
>>tags can handle. Tried setting size and maxlength attributes to 'high enough'
>>values to no avail. Does anyone know if there is another attribute, etc.
>>Documentation appears to indicate there is in fact no actual limit.
>>
>>Many thanks in advance.
>>
>>Dan
>>
>>

>