Description:
This is a follow-up on the bug that I previously closed myself, because I had
misunderstood.
I wondered, where I had read that we should use the '?' instead of '@', which is again the
recommended identifier.

Well, it turns out, that I had simply read the helpfile included (my fault, never read the
help file, lol)
Well, here are the topics, where it's recommended to use '?':

MySqlCommand Class (See 'Note' half way down)
MySqlDataAdapter..::.DeleteCommand Property (example code)
MySqlDataAdapter..::.InsertCommand Property (example code)
MySqlDataAdapter..::.SelectCommand Property  (example code)
MySqlDataAdapter..::.UpdateCommand Property  (example code)

How to repeat:
To repeat, read the helpfile

Suggested fix:
Change the help-text, so people like me don't misunderstand again :-)

To Reggie: Thanks for your mail, I chose to answer here 'officially'.

...and I totally agree, that using '@' is better. .Net users don't need user variables,
they create their own in their programs. And making converting to MySql easier is the
right choice. Now it's also easier to read MS' doc and examples.

Hi Poul and thanks for your report. Verified just as described by looking into chm file
distributed with c/NET 5.2.2. There appear to be some inconsistencies regarding this in
web help too.

A patch for this bug has been committed. After review, it may
be pushed to the relevant source trees for release in the next
version. You can access the patch from:

  http://lists.mysql.com/commits/48017

I've updated the docs that ship with the product.  The online docs should now be updated.

starting with 5.2 they should be using @ but ? will still work