ADO Client Cursor Engine

[Guest]

Hi there: This isn't exactly an Access question though it is directly related.

I believe the ADO Client Cursor Engine is installed as part of MDAC. If
that's the case, I would imagine that there are many PCs and Macs out there
that don't have the ADO Client Cursor Engine.

What would happen if I chose a client side cursor when building a web page
but the user did not have the cursor engine?

Thanks
Kurt Wimberger

 

[Sylvain Lafontaine]

What kind of web page are you talking?

If you are using ASP or ASP.NET to build your web page then there is nothing
needed on the client side.

If you are using a DAP (Data Access Page), then it is possible that the
client will have to download and install some components; however, this last
requirement is not limited to ADO and include the OWC (Office Web
Components).

 

[Guest]

Thank you Sylvain:

I am talking about classic asp. I am still confused. How can a client handle
a client-side cursor in their Mac Safari browser then? Where would they have
gotten the component to handle an ADO client cursor?

Thanks

Kurt

 

[Brendan Reynolds]

In this context, the 'client' is the ASP application, which is running on
the web server, not on the end-user's desktop. The retrieval of the data
happens on the web server, only the resulting HTML is returned to the
browser.

 

[Guest]

Thanks Brendan:

Talk about way over-thinking this. I really should have know that - dang.
Thanks for the wake up call!

Kurt