Visual Basic

Craster wrote:

The items with '@' in front refer to parameters being supplied to a stored procedure.

Craster wrote:

The only reason you should ever see this in VB code is if the code is attempting to create the stored procedure on the SQL Server - I can't see that this would ever work if you attempt to run it as an update statement directly from a VB app.

Craster wrote:

It's possible that someone's copied and pasted the code from a stored procedure directly into VB as an attempt to do an update, but I don't believe it can possibly work.

SELECT * FROM MyTable WHERE name=@name

Dim cmd As SqlCommand
cmd = New SqlCommand()
cmd.CommandText="SELECT * FROM MyTable WHERE name=@name"
cmd.Parameters.Add("@name", "John Smith")
cmd.Connection = MyConnection
Dim reader As SqlDataReader
reader = cmd.ExecuteReader()

When to Choose MSDE<br />
<br />
MSDE is an attractive option for upgrading existing Jet applications to improve scalability or for creating new desktop and shared database solutions that can be easily migrated to full SQL Server, as the solutions must need to scale.<br />
<br />
SQL Server compatibility<br />
<br />
MSDE data engines are fully compatible with SQL Server. Thus, tables, stored procedures, triggers, and any other database objects created in MSDE will operate without modification in a SQL Server database. In contrast many Jet objects, such as queries, cannot be migrated to SQL Server without modification. If you are considering migrating to SQL Server in the future, or it is likely that your database application will exceed the limitations of Jet, you should choose MSDE. Doing so will provide you with the simplest path to upsizing the database to SQL Server without changing a single line of code.