Re: SQL Connection Strings
- From: "Patrice" <http://www.chez.com/scribe/>
- Date: Mon, 17 Nov 2008 20:03:18 +0100
If this is an ASP.NET application, this is most likely caused by using
static (or VB.NET shared) variables. They are common to the whole
application and keep in mind that when using ASP.NET you have a single
application for all users, so all users are sharing the same value...
Check out all the static (shared or module level for VB.NET) variables.
--
Patrice
"Erica" <Erica@xxxxxxxxxxxxxxxxxxxxxxxxx> a écrit dans le message de groupe
de discussion : 0B7F6EEC-273D-43BD-A6E0-867625E94C7A@xxxxxxxxxxxxxxxx
Data returned from Sql through a stored procedure is dependent on what
user
is logged in. If the connection string is NOT unique, will this cause the
connections to get mixed up and cause one user to see data another user
(also
logged in) should be seeing. If not, what might cause this?
.
- References:
- SQL Connection Strings
- From: Erica
- SQL Connection Strings
- Prev by Date: SQL Connection Strings
- Next by Date: Re: SQL Connection Strings
- Previous by thread: SQL Connection Strings
- Next by thread: Re: SQL Connection Strings
- Index(es):
Relevant Pages
|