ok, ok, I finally got it. Parameters are positionally sensitive. I can't
believe I spent all this time not finding the answer to this. Surely
hundreds of folks have had this problem!
> This is reposted from the vb forum since a couple of folks there thought
> it was more suited to this forum.
[quoted text clipped - 19 lines]
> .ExecuteNonQuery()
> End With
Norman Yuan - 17 May 2005 01:19 GMT
Just a reminder: "Parameters are positionally sensitive" is only applied to
OleDbClient namespace. If you work with SQL Server, using SqlClient, your
code will be working OK. That is why many .NET samples dealing with Access
DB uses "?" in SQL statement instead of "@ParameterName". Since
@ParameterName is not used by OleDbClient, use it in code could lead to
hard-to-debug mistake, as you just experienced.
> ok, ok, I finally got it. Parameters are positionally sensitive. I can't
> believe I spent all this time not finding the answer to this. Surely
[quoted text clipped - 23 lines]
> > .ExecuteNonQuery()
> > End With
Joe Fallon - 17 May 2005 02:19 GMT
Named parameters do not work with Access and .Net code.
The order they are created is the key.
In other words they are positionally sensitive. <g>
I have run into the same issue. As have many others.

Signature
Joe Fallon
Access MVP
> ok, ok, I finally got it. Parameters are positionally sensitive. I can't
> believe I spent all this time not finding the answer to this. Surely
[quoted text clipped - 23 lines]
>> .ExecuteNonQuery()
>> End With