We have no idea what error that generates - and no access to your system or network to try and find out.
So, it's going to be up to you.
Fortunately, you have a tool available to you which will help you find out what is going on: the debugger. If you don't know how to use it then a quick Google for "Visual Studio debugger" should give you the info you need.
You swallow your exception, which contains detail on why the connection attempt failed:
try
{
mySqlConnection.Open();
return true;
}
catch(Exception ex)
{
return false;
}
The error message and detail is normally very useful!
Put a breakpoint on the first line in the function, and run your code through the debugger. Then look at your code, and at your data and work out what should happen manually. Then single step each line checking that what you expected to happen is exactly what did. When it isn't, that's when you have a problem, and you can back-track (or run it again and look more closely) to find out why.
If it throws an exception you will see that, and can examine the Exception object to see what exactly it is complaining about. (Assuming it's a connection problem). If it isn't, then you need to look at the actual error you don't catch and look at what it is saying - probably something about there being no table called "kho_k22".
Sorry, but we can't do that for you - time for you to learn a new (and very, very useful) skill: debugging!