Sorry I must be missing something. When you say "check for default schema",
I can't find it it. It is SQL 2005. I have gone to the login propeties page
of the login (in SQL 2005), gone to user mapping and put the default scheme
over to do_owner but the sql scripts generated are still this same in VS
2005
"KJ" <n_**********@Mail.comwrote in message
news:O7**************@TK2MSFTNGP03.phx.gbl...
Which version of SQL Server? If 2005, go to the properties page of the
login you are using (via Management Studio), and check the value for
Default Schema for that login. My guess is that it's not dbo. But this is
just a guess.
"Chris" <no****@nospam.comwrote in message
news:Ox**************@TK2MSFTNGP02.phx.gbl...
>No I can't find it. Any clues where abouts I might find it. I have looked
on the properties on of the dataset etc.
"KJ" <n_**********@Mail.comwrote in message
news:OF*************@TK2MSFTNGP05.phx.gbl...
>>Is there a setting for the database "Schema Name" somewhere on the
properties of the data set? That's what's being prepended to the table
name.
"Chris" <no****@nospam.comwrote in message
news:Od**************@TK2MSFTNGP02.phx.gbl...
I am trying to create a strongly typed dataset is VS 2005 with the VS
creating the stored procedures. It won't create the stored procedures.
The SQL script it generates is based on a SQL login so the script looks
something like:
DROP PROCEDURE WebManagerV2.WEB_PAGE_UPDATE
these scripts won't work until I change the script to:
DROP PROCEDURE dbo.WEB_PAGE_UPDATE
What am I doing wrong? I suspect I doing my connectionstring wrong in
some way or my permissions are wrong in SQL Server.
Regards, Chris.
