Don't "swallow" exceptions:
try {
conn.Open();
} catch (Exception ex) {
}
If the connection fails to open - and it almost certainly does from the error message you show - you have no idea why, or even that it did fail! And continuing with the rest of the method once it's failed to open? Why? Did you think it woul;d still work, even without it being open?
Uncomment the MessageBox, add a
return
to catch code (or better, enclose the rest of the method in the
try
block), and use the debugger to examine what is in the connection string when it fails to open.
And by the way: You aren't closing the connection, or calling Dispose on it either - so if it manages to open, it will lock the DB file until your app ends. Use a
using
block around DB component constructors to ensure they are automatically Closed and Disposed when you are finished with them.