Ok, so that got rid of that error now I get “no rows in result set” But again, if I run this with db.QueryRow it works perfectly. So it is something with the statement that it thinks nothing was found.
Also, do I need to be doing anything about sql injection here? I am not sure if things are getting slashed out by default or if I need to be running through other measures to insure no one can mess with my queries.
Thanks,
Glenn