Yes, I am able to connect using UniDAC by itself. I dropped a TUniConnection and set the following using the connection editor:
On Connect Tab:
Provider: MySQL
Server name was set to the Azure MySQL database server.
Port: 3306
Username and password were set correctly.
LoginPrompt was turned off (un-checked)
DBName was typed in correctly.
On Options tab:
Compress: True
Protocol: mpSSL
I saved the settings and set the TUniConnection’s Connected property to true. The TUniConnection component connected properly.
To check this I dropped a TMySQLUniProvider and a TUniTable and then checked the TUniTable’s TableName property drop-down and it properly retrieved the table nmes from the server.
I have tried adding “SpecificOptions.Protocol = mpSSL” to the DataAbstract connection string. Without that setting DA gives an error about SSL being required. With the setting DA gives the
can you show what options would be set if connection was created manually in runtime?
by other hand, you can look at .dfm and see what exactly were set.
probably UniDAC wizard sets something additionally …
Open SSL libraries are installed in the system path as well as the rad studio bin folder where bds.exe is installed and it is in the Everwood bin folder.