Showing posts with label edition. Show all posts
Showing posts with label edition. Show all posts

Wednesday, March 7, 2012

rda.pull exception

Hi,

I have followed the technical artical "Remote Data Access Synchronization with SQL Server 2005 Compact Edition and Visual Basic.NET" to create a sample application.

But when I run debug mode and get an exception unexpected as following as doing rad.pull :

Immediate Window:

A first chance exception of type 'System.Data.SqlServerCe.SqlCeException' occurred in System.Data.SqlServerCe.dll

Message Box

[Contacts]

Code:

Private Sub RADPullButton_Click(ByVal sender As System.Object, ByVal e As System.EventArgs) Handles RADPullButton.Click

Try
VerifyDatabaseExists()
Dim rda As SqlCeRemoteDataAccess
rda = GetRDAObject()
rda.Pull("Contacts", _
"SELECT CustomerID, CompanyName, ContactName, ContactTitle, Address, City, Region, PostalCode, Country, Phone, Fax FROM Customers", _
My.Settings.ServerOleDBNorthwindConnectionString, _
RdaTrackOption.TrackingOnWithIndexes, _
"Contacts_Errors")

Catch ex As Exception
MessageBox.Show(ex.ToString())
Finally
Windows.Forms.Cursor.Current = Cursors.Default
End Try

End Sub

Thanks in advance,

JD

You need to grab all the error information, by following the guidelines in this topic from SQL CE Books online - Handling Errors in Managed Applications http://msdn2.microsoft.com/en-us/library/ms174079.aspx

|||

HI ErikEJ,

I have following the link to catch real sql server compact edition error exception

Here is what I got and I still don't know what this meas:

Error Code:80004005
Message :[Contacts]
Minor Err: 28573
Source: Microsoft SQL Server Compact Edition
Err. Par.: Contacts

Thanks a lot,

JD

|||

There already is a local table with the same name as used in your RDA definition. See this very helpful post by laxmi at http://blogs.msdn.com/sqlservercompact/archive/2007/01/23/rda-subscriptions.aspx

|||

I am having a similar problem. When I pull the tables, I also create an error table (tablename_err). If I have to pull a table again, I first drop the table if it exists and then attempt to pull it again. I cannot do this though because when I drop the table, the error table does not get dropped and it will not let me pull a another error table (error 28573). I have attempted to explicitly drop the error table, but I am not allowed to do that either as that generates the 28605 error: "DDL operations on the table are restricted." I did not have this problem with SQLCE 2.0, only since I migrated to SQLMobile (3.0). How do I get rid of the original error tables so that I can pull again?

|||

One doesn't has to drop the error tables explicitly. These will be dropped automatically when the associated RDA tracked table is dropped. For e.g.:

rda.pull(@."pulltable", @."select * from foo", <conn string to SQL server>, RDATrackOption.TrackingOn, @."err_pull");

when one drops pulltable, err_pull automatically gets dropped since it is associated with pulltable which is being tracked. Please refer to "Maintaining Error Tables" in http://msdn2.microsoft.com/en-us/library/ms171782.aspx

Could you verify if you are indeed dropping all the local data tables into which you are attempting to pull data?

rda.pull exception

Hi,

I have followed the technical artical "Remote Data Access Synchronization with SQL Server 2005 Compact Edition and Visual Basic.NET" to create a sample application.

But when I run debug mode and get an exception unexpected as following as doing rad.pull :

Immediate Window:

A first chance exception of type 'System.Data.SqlServerCe.SqlCeException' occurred in System.Data.SqlServerCe.dll

Message Box

[Contacts]

Code:

Private Sub RADPullButton_Click(ByVal sender As System.Object, ByVal e As System.EventArgs) Handles RADPullButton.Click

Try
VerifyDatabaseExists()
Dim rda As SqlCeRemoteDataAccess
rda = GetRDAObject()
rda.Pull("Contacts", _
"SELECT CustomerID, CompanyName, ContactName, ContactTitle, Address, City, Region, PostalCode, Country, Phone, Fax FROM Customers", _
My.Settings.ServerOleDBNorthwindConnectionString, _
RdaTrackOption.TrackingOnWithIndexes, _
"Contacts_Errors")

Catch ex As Exception
MessageBox.Show(ex.ToString())
Finally
Windows.Forms.Cursor.Current = Cursors.Default
End Try

End Sub

Thanks in advance,

JD

You need to grab all the error information, by following the guidelines in this topic from SQL CE Books online - Handling Errors in Managed Applications http://msdn2.microsoft.com/en-us/library/ms174079.aspx

|||

HI ErikEJ,

I have following the link to catch real sql server compact edition error exception

Here is what I got and I still don't know what this meas:

Error Code:80004005
Message :[Contacts]
Minor Err: 28573
Source: Microsoft SQL Server Compact Edition
Err. Par.: Contacts

Thanks a lot,

JD

|||

There already is a local table with the same name as used in your RDA definition. See this very helpful post by laxmi at http://blogs.msdn.com/sqlservercompact/archive/2007/01/23/rda-subscriptions.aspx

|||

I am having a similar problem. When I pull the tables, I also create an error table (tablename_err). If I have to pull a table again, I first drop the table if it exists and then attempt to pull it again. I cannot do this though because when I drop the table, the error table does not get dropped and it will not let me pull a another error table (error 28573). I have attempted to explicitly drop the error table, but I am not allowed to do that either as that generates the 28605 error: "DDL operations on the table are restricted." I did not have this problem with SQLCE 2.0, only since I migrated to SQLMobile (3.0). How do I get rid of the original error tables so that I can pull again?

|||

One doesn't has to drop the error tables explicitly. These will be dropped automatically when the associated RDA tracked table is dropped. For e.g.:

rda.pull(@."pulltable", @."select * from foo", <conn string to SQL server>, RDATrackOption.TrackingOn, @."err_pull");

when one drops pulltable, err_pull automatically gets dropped since it is associated with pulltable which is being tracked. Please refer to "Maintaining Error Tables" in http://msdn2.microsoft.com/en-us/library/ms171782.aspx

Could you verify if you are indeed dropping all the local data tables into which you are attempting to pull data?

rda.pull exception

Hi,

I have followed the technical artical "Remote Data Access Synchronization with SQL Server 2005 Compact Edition and Visual Basic.NET" to create a sample application.

But when I run debug mode and get an exception unexpected as following as doing rad.pull :

Immediate Window:

A first chance exception of type 'System.Data.SqlServerCe.SqlCeException' occurred in System.Data.SqlServerCe.dll

Message Box

[Contacts]

Code:

Private Sub RADPullButton_Click(ByVal sender As System.Object, ByVal e As System.EventArgs) Handles RADPullButton.Click

Try
VerifyDatabaseExists()
Dim rda As SqlCeRemoteDataAccess
rda = GetRDAObject()
rda.Pull("Contacts", _
"SELECT CustomerID, CompanyName, ContactName, ContactTitle, Address, City, Region, PostalCode, Country, Phone, Fax FROM Customers", _
My.Settings.ServerOleDBNorthwindConnectionString, _
RdaTrackOption.TrackingOnWithIndexes, _
"Contacts_Errors")

Catch ex As Exception
MessageBox.Show(ex.ToString())
Finally
Windows.Forms.Cursor.Current = Cursors.Default
End Try

End Sub

Thanks in advance,

JD

You need to grab all the error information, by following the guidelines in this topic from SQL CE Books online - Handling Errors in Managed Applications http://msdn2.microsoft.com/en-us/library/ms174079.aspx

|||

HI ErikEJ,

I have following the link to catch real sql server compact edition error exception

Here is what I got and I still don't know what this meas:

Error Code:80004005
Message :[Contacts]
Minor Err: 28573
Source: Microsoft SQL Server Compact Edition
Err. Par.: Contacts

Thanks a lot,

JD

|||

There already is a local table with the same name as used in your RDA definition. See this very helpful post by laxmi at http://blogs.msdn.com/sqlservercompact/archive/2007/01/23/rda-subscriptions.aspx

|||

I am having a similar problem. When I pull the tables, I also create an error table (tablename_err). If I have to pull a table again, I first drop the table if it exists and then attempt to pull it again. I cannot do this though because when I drop the table, the error table does not get dropped and it will not let me pull a another error table (error 28573). I have attempted to explicitly drop the error table, but I am not allowed to do that either as that generates the 28605 error: "DDL operations on the table are restricted." I did not have this problem with SQLCE 2.0, only since I migrated to SQLMobile (3.0). How do I get rid of the original error tables so that I can pull again?

|||

One doesn't has to drop the error tables explicitly. These will be dropped automatically when the associated RDA tracked table is dropped. For e.g.:

rda.pull(@."pulltable", @."select * from foo", <conn string to SQL server>, RDATrackOption.TrackingOn, @."err_pull");

when one drops pulltable, err_pull automatically gets dropped since it is associated with pulltable which is being tracked. Please refer to "Maintaining Error Tables" in http://msdn2.microsoft.com/en-us/library/ms171782.aspx

Could you verify if you are indeed dropping all the local data tables into which you are attempting to pull data?

RDA Push fails with SQL Server 2005 Compact Edition

Hello
I have a SQL Server 2005 (build 9.0.3050) database with tables belonging to
different schemas. I am in the process of developing a Windows Mobile 5.0
application that will work against this database, and Iâ'm planning to use
Remote Data Access with SQL Server 2005 CE to synch data.
I have my RDA all set up and working correctly IIS-wise, and have no problem
pulling a table from my database. However, when I attempt to push a modified
table back to the database, I get an â'Internal error: Failure setting up
bindings, possibly caused by insufficient permissions.â' error (which equates
to error 28621: SSCE_M_BINDINGS), which according to
http://msdn2.microsoft.com/en-us/library/ms172898.aspx is an internal error
which â'cannot be resolved by common troubleshooting techniquesâ'. The
â'insufficient permissionsâ' is a red herring I think, since the problem
persists even if the SQL Server login that is being used for RDA is in the
sysadmin role.
Iâ've attempted to identify the problem by starting from scratch with a new
database and a new table with a couple of test columns. With the table
freshly created as dbo.TableName RDA works fine. However, when I create a
schema and transfer the table to the schema, RDA push fails as above, so to
me it looks like the schema is causing the problem.
Anyone any ideas about this? All help greatly appreciated!
Thanks - GrahamIn case this helps anyone else, I lodged a support call with Microsoft about
this and it has been confirmed that "SQL Server Compact Edition does not
support RDA.Push for non-default Schema tables". Hopefully this will be
fixed in the future.
"GrahamS" wrote:
> Hello
> I have a SQL Server 2005 (build 9.0.3050) database with tables belonging to
> different schemas. I am in the process of developing a Windows Mobile 5.0
> application that will work against this database, and Iâ'm planning to use
> Remote Data Access with SQL Server 2005 CE to synch data.
> I have my RDA all set up and working correctly IIS-wise, and have no problem
> pulling a table from my database. However, when I attempt to push a modified
> table back to the database, I get an â'Internal error: Failure setting up
> bindings, possibly caused by insufficient permissions.â' error (which equates
> to error 28621: SSCE_M_BINDINGS), which according to
> http://msdn2.microsoft.com/en-us/library/ms172898.aspx is an internal error
> which â'cannot be resolved by common troubleshooting techniquesâ'. The
> â'insufficient permissionsâ' is a red herring I think, since the problem
> persists even if the SQL Server login that is being used for RDA is in the
> sysadmin role.
> Iâ've attempted to identify the problem by starting from scratch with a new
> database and a new table with a couple of test columns. With the table
> freshly created as dbo.TableName RDA works fine. However, when I create a
> schema and transfer the table to the schema, RDA push fails as above, so to
> me it looks like the schema is causing the problem.
> Anyone any ideas about this? All help greatly appreciated!
> Thanks - Graham|||There is a workaround for this problem - you can use a synonym in place of
the base table name. Crucially, the synonym must be named the same as the
base table ie 'CREATE SYNONYM dbo.MyTable FOR MySchema.MyTable'.
"GrahamS" wrote:
> In case this helps anyone else, I lodged a support call with Microsoft about
> this and it has been confirmed that "SQL Server Compact Edition does not
> support RDA.Push for non-default Schema tables". Hopefully this will be
> fixed in the future.
> "GrahamS" wrote:
> > Hello
> >
> > I have a SQL Server 2005 (build 9.0.3050) database with tables belonging to
> > different schemas. I am in the process of developing a Windows Mobile 5.0
> > application that will work against this database, and Iâ'm planning to use
> > Remote Data Access with SQL Server 2005 CE to synch data.
> >
> > I have my RDA all set up and working correctly IIS-wise, and have no problem
> > pulling a table from my database. However, when I attempt to push a modified
> > table back to the database, I get an â'Internal error: Failure setting up
> > bindings, possibly caused by insufficient permissions.â' error (which equates
> > to error 28621: SSCE_M_BINDINGS), which according to
> > http://msdn2.microsoft.com/en-us/library/ms172898.aspx is an internal error
> > which â'cannot be resolved by common troubleshooting techniquesâ'. The
> > â'insufficient permissionsâ' is a red herring I think, since the problem
> > persists even if the SQL Server login that is being used for RDA is in the
> > sysadmin role.
> >
> > Iâ've attempted to identify the problem by starting from scratch with a new
> > database and a new table with a couple of test columns. With the table
> > freshly created as dbo.TableName RDA works fine. However, when I create a
> > schema and transfer the table to the schema, RDA push fails as above, so to
> > me it looks like the schema is causing the problem.
> >
> > Anyone any ideas about this? All help greatly appreciated!
> >
> > Thanks - Graham

RDA Push fails with SQL Server 2005 Compact Edition

Hello

I have a SQL Server 2005 (build 9.0.3050) database with tables belonging to
different schemas. I am in the process of developing a Windows Mobile 5.0
application that will work against this database, and I’m planning to use
Remote Data Access with SQL Server 2005 CE to synch data.

I have my RDA all set up and working correctly IIS-wise, and have no problem
pulling a table from my database. However, when I attempt to push a modified
table back to the database, I get an ‘Internal error: Failure setting up
bindings, possibly caused by insufficient permissions.’ error (which equates
to error 28621: SSCE_M_BINDINGS), which according to
http://msdn2.microsoft.com/en-us/library/ms172898.aspx is an internal error
which “cannot be resolved by common troubleshooting techniques”. The
‘insufficient permissions’ is a red herring I think, since the problem
persists even if the SQL Server login that is being used for RDA is in the
sysadmin role.

I’ve attempted to identify the problem by starting from scratch with a new
database and a new table with a couple of test columns. With the table
freshly created as dbo.TableName RDA works fine. However, when I create a
schema and transfer the table to the schema, RDA push fails as above, so to
me it looks like the schema is causing the problem.

Anyone any ideas about this? All help greatly appreciated!

Thanks - Graham

In case this helps anyone else, I lodged a support call with Microsoft about
this and it has been confirmed that "SQL Server Compact Edition does not
support RDA.Push for non-default Schema tables". Hopefully this will be
fixed in the future.
|||There is a workaround for this problem - you can use a synonym in place of the base table name. Crucially, the synonym must be named the same as the base table ie 'CREATE SYNONYM dbo.MyTable FOR MySchema.MyTable'.

RDA Push fails with SQL Server 2005 Compact Edition

Hello

I have a SQL Server 2005 (build 9.0.3050) database with tables belonging to
different schemas. I am in the process of developing a Windows Mobile 5.0
application that will work against this database, and I’m planning to use
Remote Data Access with SQL Server 2005 CE to synch data.

I have my RDA all set up and working correctly IIS-wise, and have no problem
pulling a table from my database. However, when I attempt to push a modified
table back to the database, I get an ‘Internal error: Failure setting up
bindings, possibly caused by insufficient permissions.’ error (which equates
to error 28621: SSCE_M_BINDINGS), which according to
http://msdn2.microsoft.com/en-us/library/ms172898.aspx is an internal error
which “cannot be resolved by common troubleshooting techniques”. The
‘insufficient permissions’ is a red herring I think, since the problem
persists even if the SQL Server login that is being used for RDA is in the
sysadmin role.

I’ve attempted to identify the problem by starting from scratch with a new
database and a new table with a couple of test columns. With the table
freshly created as dbo.TableName RDA works fine. However, when I create a
schema and transfer the table to the schema, RDA push fails as above, so to
me it looks like the schema is causing the problem.

Anyone any ideas about this? All help greatly appreciated!

Thanks - Graham

In case this helps anyone else, I lodged a support call with Microsoft about
this and it has been confirmed that "SQL Server Compact Edition does not
support RDA.Push for non-default Schema tables". Hopefully this will be
fixed in the future.
|||There is a workaround for this problem - you can use a synonym in place of the base table name. Crucially, the synonym must be named the same as the base table ie 'CREATE SYNONYM dbo.MyTable FOR MySchema.MyTable'.

Saturday, February 25, 2012

RDA Pull Fail

I try to pull data from SQL 2005 Express Edition to SQL Mobile 5.0, with Visual Basic 2005.
It keep prompt me the error Native Error:

System.Data.SqlServerCe.SqlCeException was unhandled
HResult=-2147024809
Message="An error has occurred on the computer running IIS. Try restarting the IIS server."
NativeError=28022
Source="Microsoft SQL Server 2005 Mobile Edition"
StackTrace:
at System.Data.SqlServerCe.NativeMethods.CheckHRESULT()
at System.Data.SqlServerCe.SqlCeRemoteDataAccess.Pull()
at PDA2007.PULLPUSH.btn_pull_Click()
at System.Windows.Forms.Control.OnClick()
at System.Windows.Forms.Button.OnClick()
at System.Windows.Forms.ButtonBase.WnProc()
at System.Windows.Forms.Control._InternalWnProc()
at Microsoft.AGL.Forms.EVL.EnterMainLoop()
at System.Windows.Forms.Application.Run()
at PDA2007.PULLPUSH.Main()

Below is my coding :

Private Sub btn_pull_Click(ByVal sender As System.Object, ByVal e As

System.EventArgs) Handles btn_pull.Click


Const gRemoteProvider = "Provider=SQLOLEDB.1;Persist Security

Info=False; " & _


"User ID=dmspda;Password=dmspda;Initial

Catalog=dmspda;Data Source=INSPIRON6000"


Const gInternetURL = "HTTP://192.168.1.3/Sync/SSCESA30.DLL"


Const gInternetLogin = "INSPIRON6000\IUSR_INSPIRON6000"


Const gInternetPwd = ""


Dim rda As SqlCeRemoteDataAccess



rda = New SqlCeRemoteDataAccess


rda.LocalConnectionString = "Data Source=\My Documents\pda.sdf"


rda.InternetUrl = gInternetURL


rda.InternetLogin = gInternetLogin


rda.InternetPassword = gInternetPwd



rda.Pull("pda_uom", "Select * from pda_uom", gRemoteProvider,

RdaTrackOption.TrackingOn)



End Sub


I have been refer to a lot of website and read articles, help forum, have try to disable Firewall, allow HTTP and HTTPS, uninstall anti-virus system. I have no idea, what is this problem and how to solve it ? If you face same problem before, hope can give some comment here, appreciate it!

Developed Machine:
* XP Pro S2
* SQL Server 2005 Express Edition
* Visual Studio 2005

Device :
* SQL Mobile 2005
* Window Mobile 5.0



Hullo xiaoytan

I have facing the same error as u faced, could u solved this pbm, then please let me know , how to do it ?

Thank u.

RDA Pull error using Microsoft SQL Server Compact Edition 2005

Hello dear all.

I am using a Compact Framework 2.0 on a mobile 5.0 with a local Microsoft SQL Compact Edition 2005 database. The backend database is a Microsoft SQL Server 2005 and I am trying to pull a 45000 rows table (the table has 2 varchars(8) forming a primary key and an INTEGER column).

The statement I issue is the following:

rda.Pull(table.TableName, table.TableQuery, Program.RdaOleDbConnectionString, RdaTrackOption.TrackingOnWithIndexes, table.TableName + "Errors");

The application works perfectly when I am pulling smaller tables (up to 15000 rows) but when I try to pull this one I get the following error details:

sqlCeEx
{""}
base {System.SystemException}: {""}
Errors: {System.Data.SqlServerCe.SqlCeErrorCollection}
errors: {System.Data.SqlServerCe.SqlCeErrorCollection}
HResult: -2147024882
Message: ""
NativeError: 0
Source: "Microsoft SQL Server Compact Edition"

Please have in mind that the handheld on which I deploy does not have an extra storage card.

I have done a thorough internet search and I have found no solution to this problem. I truly rely on you to find the solution.

Thanks in advance,

Steliosvcy.

http://msdn.microsoft.com/library/default.asp?url=/library/en-us/dnsqlce/html/sqlce_troubleconnect.asp

Sounds like a timeout error to me.

HRESULT = -2147012894 = FFFFFFFF80072EE2

Take the 2EE2, Convert back to decimal (12002).
Lookup the error in wininet.h (C:\program files\windows ce something\something\include

//
// Internet API error returns
//

#define INTERNET_ERROR_BASE 12000
#define ERROR_INTERNET_TIMEOUT (INTERNET_ERROR_BASE + 2)

How to fix it? Gawd knows. Change the timeout? Let me know how to do that if you find out!! (That's what I'm trying to do at the moment)

Regards,

James.
|||

You can set the oledb timeout (from IIS to SQL) with: Connect Timeout=180 in the connection string (3 minutes in this case).

Code Snippet

Provider=SQLOLEDB; Data Source=mySQLServer; Initial Catalog=NorthWind; user id=sa; password=; Connect Timeout=180;

You may have to adjust to fit your environment.

|||

SqlCeReplication and SqlCeRemoteDataAccess. Both of these have SendTimeout, ReceiveTimeout for IIS connectivity and SQL Server connectivity can be controlled by OLEDB connection string or QueryTimeout on REPL/RDA Object.

Thanks,

Laxmi

RDA Pull error using Microsoft SQL Server Compact Edition 2005

Hello dear all.

I am using a Compact Framework 2.0 on a mobile 5.0 with a local Microsoft SQL Compact Edition 2005 database. The backend database is a Microsoft SQL Server 2005 and I am trying to pull a 45000 rows table (the table has 2 varchars(8) forming a primary key and an INTEGER column).

The statement I issue is the following:

rda.Pull(table.TableName, table.TableQuery, Program.RdaOleDbConnectionString, RdaTrackOption.TrackingOnWithIndexes, table.TableName + "Errors");

The application works perfectly when I am pulling smaller tables (up to 15000 rows) but when I try to pull this one I get the following error details:

sqlCeEx
{""}
base {System.SystemException}: {""}
Errors: {System.Data.SqlServerCe.SqlCeErrorCollection}
errors: {System.Data.SqlServerCe.SqlCeErrorCollection}
HResult: -2147024882
Message: ""
NativeError: 0
Source: "Microsoft SQL Server Compact Edition"

Please have in mind that the handheld on which I deploy does not have an extra storage card.

I have done a thorough internet search and I have found no solution to this problem. I truly rely on you to find the solution.

Thanks in advance,

Steliosvcy.

http://msdn.microsoft.com/library/default.asp?url=/library/en-us/dnsqlce/html/sqlce_troubleconnect.asp

Sounds like a timeout error to me.

HRESULT = -2147012894 = FFFFFFFF80072EE2

Take the 2EE2, Convert back to decimal (12002).
Lookup the error in wininet.h (C:\program files\windows ce something\something\include

//
// Internet API error returns
//

#define INTERNET_ERROR_BASE 12000
#define ERROR_INTERNET_TIMEOUT (INTERNET_ERROR_BASE + 2)

How to fix it? Gawd knows. Change the timeout? Let me know how to do that if you find out!! (That's what I'm trying to do at the moment)

Regards,

James.
|||

You can set the oledb timeout (from IIS to SQL) with: Connect Timeout=180 in the connection string (3 minutes in this case).

Code Snippet

Provider=SQLOLEDB; Data Source=mySQLServer; Initial Catalog=NorthWind; user id=sa; password=; Connect Timeout=180;

You may have to adjust to fit your environment.

|||

SqlCeReplication and SqlCeRemoteDataAccess. Both of these have SendTimeout, ReceiveTimeout for IIS connectivity and SQL Server connectivity can be controlled by OLEDB connection string or QueryTimeout on REPL/RDA Object.

Thanks,

Laxmi

Monday, February 20, 2012

Rather odd functionality in Management Studio

Hi,

I have found some nice functionality in SQL Server Management Studio (I'm using the Developer Edition) that appears to me to be about reverse from what it should be.

If you start to create a View, the Query Designer opens. If you add a Parameter to your query, you get an error message saying that it is not valid in this type of query (of course). If you continue and then execute the query, a nice dialogue opens and invites you to enter the values to complete running the query. Nice, you can test your SQL. But of course you can't save. (You could cut and paste the tested SQL of course).

You get the same functionality when adding a query using VS2005 dataset designer, but here it is called the Query Builder! And without the error message of course.

On the otherhand, start to create a new Query, a text editor opens. Right click to start the Query Designer. Now write the same query, but there is no ability to run from the Designer. Close the designer, and if you try to run, you get an error message because the SQL is not parsed for the parameters!

Have others found this and thought it odd?

Thanks

John

Yes, this is odd and based ont he fact that the two UIs are own by different program groups at Microsoft. in further versions they will be aligned but until then you will have the different behaviour.

Jens K. Suessmeyer.

http://www.sqlserver2005.de