"Lee Silver" <LSilverinformation-concepts.com> wroteNo, because you will be using Connection Pooling.> In the current VB6 app, the user logs into the db once, does a whole lot of
> things across 7-15 screens, and gets logged off the db as he exits the app.
> If I understand you correctly, in the ASP.NET version he would be logged in and
> out for each screen. Won't that be rather time consuming?
Microsoft ASP.NET MVP
> // Lee Silver
> // Information Concepts Inc.
> // [url]http://www.information-concepts.com[/url]
> Facilitating the automated conversion of Data into Information
> since 1982
>>> > "Lee Silver" <LSilverinformation-concepts.com> wrote
> >> >> >>We have an existing VB6 app that a number of external users want converted to be
> >>a Web app.
> >>The business and db layers are in VB6 Com Dll's; which we obviously want to
> >>leverage as much as possible.
> >>I know an ADO.NET Connection should not be stored as a Session-variable; but
> >>does the same hold true for an ADO Connection?
> > Correct, do not store the Connection object in a Session var. Just open and
> > close the connection as needed on each web page (use Connection Pooling).
> > You can (if you want) stored the connection **string** in a Session or
> > Application var.