Download a C64 or Atari simulator. Voila - BASIC. And you can do cool things like poke characters on the screen, write garbage into the keyboard buffer, and create your own 8-bit chip tunes!

I figured out my own problem just after posting the message. It was a subtle syntactical error. Nonetheless, I have spent many days trying to debug datatype errors, in which using cmd.Parameters.AddWithValue(...) couldn't seem to get the type right. Finally I began adding the parameters first, with the type specified using cmd.Parameters.Add(..., type) and then adding the value to the parameter. So far this has eliminated the frustrations of my commands not working. However, the jury is still out for me as to whether using parameters is THAT much more convenient or less work that concatenating values into a string. I have a pretty good system worked out where I separate each concatenated value on a separate line my code (for readability) and use a quote(arg) function and formatDate(arg) function for convenience. Public Function quote(arg as String) as String Return chr(34) + arg + chr(34) End Function You get the idea. I find it simpler to debug a query in which I can see all the values by simply printing the string to the debug window, rather than iterating through the parameters collection manually in the immediate window.

[Message Deleted]

Does anyone else get as frustrated as me trying to use Parameters with queries? How much time do you spend trying to fix "Datatype mismatch in criteria expression" or other such errors? I find these errors nearly impossible to debug and fix. There's no way I can find out which parameter is not correct. Using Parameters is supposed to make creating complex queries neat and easy, but using Parameters has been nothing but a frustration for me.

Are you using a third party control, like Crystal Report Control? I kept having this error when trying to display a Report. The report control was getting an error, it just doesn't know how to report it to .NET. There was something wrong with my report. Once I got the report fixed, everything was fine.

I'm using Wizard generated controls in a database project. I have a dataset, bindingsource, and table adapter. There is a datagrid bound to the binding source. I'm trying to call RemoveAt() on the binding source, but it throws an error indicating that the list is FixedSize and cannot be modified. How do I fix this? Thanks in advance.