Re: ADO works ADO.NET does
From: Patrice (nobody_at_nowhere.com)
Date: 11/16/04
- Next message: Kishan Hathiwala: "Retrieve the last entered record"
- Previous message: Kris Desmadryl: "Re: A DbDataAdapter issue"
- In reply to: resolutionsnet: "ADO works ADO.NET does"
- Next in thread: resolutionsnet: "RE: ADO works ADO.NET does"
- Messages sorted by: [ date ] [ thread ]
Date: Tue, 16 Nov 2004 11:41:21 +0100
Try SQL profiler to check the user name is the one you expect... You could
also retrive the DB name, the user name instead of calling the stroed proc
to make sure you are in the expected context...
Patrice
-- "resolutionsnet" <resolutionsnet@discussions.microsoft.com> a écrit dans le message de news:021D4193-09BF-4A5E-9D10-1DF92E8DC739@microsoft.com... > I have a strange issue and wondered if anyone could shed some light on the > situation. > > I have two applications (sitting on web server A), one is a VB website using > ADO and one is a VB.NET using ADO.NET. They both connect to the same SQL > Server, with the same user id and password. The VB application can connect > and execute stored procedure X, but when the ADO.NET application tries it > receives a SQL Server does not exist error message. These two application do > exactly the thing, just call one stored procedure. I have gone through > various DSN settings, but none work. Even if I bring down the applications to > my server, the same results happen. > > Any Ideas? >
- Next message: Kishan Hathiwala: "Retrieve the last entered record"
- Previous message: Kris Desmadryl: "Re: A DbDataAdapter issue"
- In reply to: resolutionsnet: "ADO works ADO.NET does"
- Next in thread: resolutionsnet: "RE: ADO works ADO.NET does"
- Messages sorted by: [ date ] [ thread ]
Relevant Pages
|