Re: Engine Type - Michael Louie Loria - com.mysql.lists.win32

6 messages in com.mysql.lists.win32Re: Engine Type

From	Sent On	Attachments
Michael Louie Loria	13 Jul 2005 03:42
SGr...@unimin.com	13 Jul 2005 06:35
jbon...@sola.com.au	13 Jul 2005 17:26
Michael Louie Loria	13 Jul 2005 18:15
jbon...@sola.com.au	13 Jul 2005 22:02
Michael Louie Loria	13 Jul 2005 22:44

Subject:	Re: Engine Type
From:	Michael Louie Loria (mich...@yahoo.com)
Date:	07/13/2005 10:44:24 PM
List:	com.mysql.lists.win32

-----BEGIN PGP SIGNED MESSAGE----- Hash: RIPEMD160

jbon...@sola.com.au wrote:

I think either table engine would be OK but InnoDB has some good extra features and is the default in recent versions of MySQL so I would go with that.

Now about your connection problem....

You need to check the following things in this order.

Can you get to the server machine on the network? Ping should check that. If not some routing tables may need to be changed. Consult your networking people.

Can you get to the MySQL port (usually 3306 but might be different)? I'm not sure how you check that.

If you get this far you should get some response from MySQL even if it is just to tell you that access is denied. If that happens it is a MySQL permissions problem. Make sure the user you are logging in as (to MySQL) has permission to log in from the host where you are running the client.

How far do you get when you try to connect your client to the MySQL server? Do you get any error messages? Make sure your VB6 application fully reports any errors that happen on the database connection. (It will depend on how you are connecting how you do that.)

John B.

I think I stick with InnoDB. I already fixed, it was not the problem of MySQL. It was the fault of the VPN. I change my encryption to 3DES frm AES-256 and it worked. I think it had to do something with my key size which is only 1024.

Thanks for da help,

iD8DBQFCr0N9EWLHf0olbsgRA3QeAJwKJEt3BLmuNRPf99AKmyZEHYMriQCfcVcd zgyStn3UcOkHx/RRcbsrY9E= =SSIa -----END PGP SIGNATURE-----