I've written a working VB.NET app with a SQLServer
database back end. In migration, I am trying to
reconfigure a SQL Data Adpter to point to a staging
database running on a dedicated databse server to which
I have replicated my schema and all my data.
Initially it appears that the Sql Data Adaptor wizard
clearly sees all the Select, Insert, Update and Delete
stored procedures and all their parameters. When
it comes to generating statements and mappings it only
succeeds for the 'Select' stored proc and fails for the
other three citing:
The stored procedure "spInsert" could not be found in the
The stored procedure "spUpdate" could not be found in the
The stored procedure "spDelete" could not be found in the
One thing that is different from configuring the data
adapter for the local server is that the stored
procs are listed as 'dbo.procname' while originally they
were listed as just 'procname'
The developer account that I am using has been given
EXEC permission to the stored procs and SELECT, INSERT,
UPDATE & DELETE permission on all the tables involved
at a group level.
What am I doing wrong? Is this a bug with the .NET
sql data adapter confugration wizard?
Any clues will be great appreciated.