Huh.... Okay, here is what I just did. I use EM under my NT permissions. Created a northwind SP, and it failed as expected. I dropped that SP.
I used QA, still using my NT permissions, created the same northwind SP, and it worked. This looks like something really really buggy here folks. To whom should I submit this? Not sure whether it is an SQL or a VB problem. I've never encountered anything like it from the SQL side before... Hrmm.... =Blain -----Original Message----- From: The DOTNET list will be retired 7/1/02 [mailto:[EMAIL PROTECTED]] On Behalf Of Greg Reinacker Sent: Tuesday, June 11, 2002 8:43 AM To: [EMAIL PROTECTED] Subject: Re: [DOTNET] Super simple DataAdapter quesiton... I've seen this same behavior; unbelievably frustrating. I never did completely track it down, but here's what I was doing and how I got around it. I only saw the problem when I created SQL Server stored procedures through the VS.NET designer. In VS.NET, I was connecting to the database as a non-sa account, and creating the stored procedures with the designer. When I went to use them as you describe, I saw the same error. I poured over the SQL Server security settings to no avail; couldn't find anything. To fix it, I deleted all of the stored procedures, re-logged into SQL server with SQL Enterprise Manager as sa, and added the stored procedures back in. No problems then. I think it was more to do with logging in as sa than it was using the VS designer, but as I said, I never completely tracked it down. Hope this helps... Greg Reinacker Reinacker & Associates, Inc. http://www.rassoc.com http://www.rassoc.com/gregr/weblog/ -----Original Message----- From: The DOTNET list will be retired 7/1/02 [mailto:[EMAIL PROTECTED]] On Behalf Of Blain Timberlake Sent: Monday, June 10, 2002 1:57 PM To: [EMAIL PROTECTED] Subject: Super simple DataAdapter quesiton... I saw a similar question on Usenet from October, but it hadn't been answered... I open a brand new project, and drag over an SQL connection. I drag over a SQLDataAdapter as well. For the Select function of the DataAdapter I point it to a stored procedure 'ListPrinters'. It looks like everything is happy but when I go to preview the data I get: "Can't create a child list for field dbo." Now of course there is no DBO field, if I look at the commandtext object it has: dbo.[ListPrinters] If I log in through QA I can run it without the dbo. Prefix, but if I take out the dbo. Prefix in the command text I get: "Invalid Property Value The Stored procedure 'ListPrinters' could not be found in the database." The user definitely defaults to the right database. The connectionstring points to the right database. He has permission to access it as it works fine through QA. What's going on here? =Blain You can read messages from the DOTNET archive, unsubscribe from DOTNET, or subscribe to other DevelopMentor lists at http://discuss.develop.com. You can read messages from the DOTNET archive, unsubscribe from DOTNET, or subscribe to other DevelopMentor lists at http://discuss.develop.com. You can read messages from the DOTNET archive, unsubscribe from DOTNET, or subscribe to other DevelopMentor lists at http://discuss.develop.com.
