Blake,

I've been able to reproduce the problem now, it certainly
is wierd - especially since if I login as SA it all works
perfectly. So, it could be a permissions issue but I can't
think what, but it might also have something to do with
populating a DataSet because I noticed some wierd behaviour
while I was playing with that. If no one here can solve it
(I can't figure it out at the moment) then I would call the
product support number. If you have an MSDN subscription I
think you get some free (not sure). Under Help in VS.NET
they have a Technical Support link.

You could report it as a bug but by using support you
might be able to track the problem to resolution.

----------------------------------------
- Mitch Denny
- [EMAIL PROTECTED]
- +61 (414) 610-141
-

-----Original Message-----
From: The DOTNET list will be retired 7/1/02
[mailto:[EMAIL PROTECTED]] On Behalf Of Blain Timberlake
Sent: Tuesday, 11 June 2002 22:59
To: [EMAIL PROTECTED]
Subject: Re: [DOTNET] Super simple DataAdapter quesiton...


Certainly reproducible (on both our dev machines here anyway).

In EM for SQL, go into Northwind and create a new SP:

CREATE PROCEDURE [dbo].[ListCustomers]
AS
select * from customers
GO

Create an SQL user, give them access to that database and exec
permissions on that SP.

Now open Visual Studio .net.  Create a new app.  Make a connection there
using your new user.  Drag the connection on.  Drag a DataAdapter over,
go through its config steps.  Note that when you point it to the SP it
gets the field names properly.  Finish that up.  Now try to preview the
data.

"Can't create a child list for field dbo"

Now open up QA, log in as the same user and switch to Northwind
Type:

Exec ListCustomers
Or
Exec [dbo].[ListCustomers]
Or
Exec dbo.ListCustomers

And everything works hunky dorey.  Yeah I know the biases against the
designers.  The fact is that we don't have many programmers here.  Which
means that most apps are not supported by a programmer.  So anything we
can make graphical and easy means that it will get supported, and that
we don't have to devote a valuable resource to it.

Thanks,
=Blain

-----Original Message-----
From: The DOTNET list will be retired 7/1/02
[mailto:[EMAIL PROTECTED]] On Behalf Of Mitch Denny
Sent: Tuesday, June 11, 2002 8:41 AM
To: [EMAIL PROTECTED]
Subject: Re: [DOTNET] Super simple DataAdapter quesiton...

Blain,

Can you reproduce step by step using the Northwind or
Pubs databases or is the behaviour specific to the
database that you are are working with?

Make sure you list what to do step by step because
just following your instructions before, there were
a few ambiguities. The other thing is that I'd guess
that if you surveyed the majority of participants
on this list that they would avoid using the designer
for alot of this sort of stuff.

----------------------------------------
- Mitch Denny
- [EMAIL PROTECTED]
- +61 (414) 610-141
-

-----Original Message-----
From: The DOTNET list will be retired 7/1/02
[mailto:[EMAIL PROTECTED]] On Behalf Of Blain Timberlake
Sent: Tuesday, 11 June 2002 21:08
To: [EMAIL PROTECTED]
Subject: Re: [DOTNET] Super simple DataAdapter quesiton...


Am I not getting a response because:

A) This is a bad question and I'm just doing something idiotic

B) It's a flakey behaviour no one else has seen

C) There is no answer

Or

D) None of the above

???

=Blain

-----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 3:57 PM
To: [EMAIL PROTECTED]
Subject: [DOTNET] 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.

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.

Reply via email to