SQL 2005 Express and VS .Net 2003 wizard error More options



Sorry for being late to the party.

I had this problem last night and puzzled over it at length. I came on
this problem as I was reverting to VS2003 to avoid instability
problems with the same program written in VS2005!!!!!!!

my way around this (which requries no re-install and works) is as
follows, and is for the assistance of anyone else following in our
footsteps.

Open the server explorer panel
Add a new connection
Go to the Provider tab and select SQL NAtive Client (DON'T use oledb
the default "oledb provider for SQLSERVER")
Go back to the Connection tab and carry on setting up the connection
as normal

Now Drag a table from this database connection onto any form/ APSX
page.

Viola! it will now set up an adapter with the required INSERT, UPDATE,
DELETE commands.
NOTE: its no longer a SQLDataAdapter but an oledbdataadapter!

ONE Nasty gotcha: Paramterisation of queries (in oledb) requires you
to use ? instead of @p1 in your SQL Syntax, otherwise it behaves as
expected.

Also if you set your connectionstring to be dynamic (i.e. saved in an
app.config) and the server is an instance server\instance you will
have problems with the \ in the app.config. to get over this make the
" delimiters around the server instance name &qout; instead.

e.g. "Server\SQL2005"

On 6 Sep 2006, 21:21, surfr...@xxxxxxxxxxx wrote:
Hi,

I have installed Visual Studio 2005 Professional and then Visual Studio
.Net 2003 on my machine. The reason for the older version is that my
study examples are in 2003 format. I have SQL Server 2005 Express
installed and added the Northwind DB to it via the Access 2003 upsizingwizard.

In VS 2003 I have added a SQLConnection to my SQL Server 2005 Express
Northwind DB. This works fine. I then added aSQLDataAdapterand ran
thewizard. After I have run the query builder and click next I get
"There were errors configuring the data adapter" for the INSERT, UPDATE
and DELETE statements.

How do I fix this error and will VS 2003 work with SQL 2005 Express?

Another query which I cant fix is
"Visual Studio 2005 and Access database mystery"http://groups.google.co.za/group/microsoft.public.dotnet.framework.ad...

Please help me sort out these problems.

Thanks

SurfRat.

.



Relevant Pages

  • Re: Connection issues between .Net framwok and SQl Express 2005
    ... You will no longer need the database MDF file name in the connection string. ... simply attach the ASPNETDB.mdf to SQL Server permenantly, ... as USER INSTANCE on existing SQL Server Express, ...
    (microsoft.public.dotnet.framework.aspnet)
  • Re: Performance of ODBC
    ... if you have a software firewall; forward 1433/1434 to your server ... I've now created my own server with SQL Server 2005 Express, ... glitch concerns the Upsizing Wizard. ... I originally set up my ODBC connection via ...
    (microsoft.public.access.adp.sqlserver)
  • Re: Timeout problem with SS2K, VS03
    ... I noticed calls in sql profiler: ... This is the server side debug stored procedure. ... a timeout issue that I cannot identify the source of. ... transaction is committed and the connection is closed cleanly and all ...
    (microsoft.public.dotnet.framework.adonet)
  • Re: Cannot connect to SQL Express on 2003 Machine from XP machine
    ... listening on UDP 1434 using netstat -abn, ... And i double checked the connection string, and i did have it the right ... But I have another 2000 server that I can connect to fine, ... I am trying to connect from an XP SP2 machine remotely to a SQL Express ...
    (microsoft.public.sqlserver.connect)
  • Re: TQL Debugger im SQL Server 2005
    ... SQL Client Verbindung ist mit dem "sa" erstellt. ... im Visual Studio - new Project - habe ich keine Database ... >> Ich habe den SQL Server 2005 Developer Edition mit SQL Server Database ... >> Services, Analysis Services, Integration Services und Client ...
    (microsoft.public.de.sqlserver)