G
Guest
I have a web application where people have to login to use the system.
I have my own login system and a database which stores login details.
ASP.NET pages are written with VB as code behind.
I am using ADO as it is a lot easier than ADO.NET.
(Note: I have an ADO class that I can call on any webpage and get the result
with one line of code...could not get anything to work in a similar manner in
ADO.NET)
Now here is my question,
I run profiler to trace issues on the page. There is no way of telling who
is running which query and which page is calling that offending query (500+
page site). Is there a way to add username and pagename to the
connectionstring so that my 10+ hours debug per problem can be reduced to
minutes?
I have my own login system and a database which stores login details.
ASP.NET pages are written with VB as code behind.
I am using ADO as it is a lot easier than ADO.NET.
(Note: I have an ADO class that I can call on any webpage and get the result
with one line of code...could not get anything to work in a similar manner in
ADO.NET)
Now here is my question,
I run profiler to trace issues on the page. There is no way of telling who
is running which query and which page is calling that offending query (500+
page site). Is there a way to add username and pagename to the
connectionstring so that my 10+ hours debug per problem can be reduced to
minutes?