I bought and installed ODBC Administrator in order to directly import members data from my server to Filemaker. But I only get errors

[color:red]1. ODCB Error: [Actual][MySQL] lost connection to MySQL server during query. Why it always lose the connection?

[color:red]2. This file could not be translated using the selected file type. There is no option (greyed out) to choose?

What am I missing here?

G'day,

I just had the same error message. The way I fixed my issue was by ensuring that all the details entered were correct. Go back first to your ODBC setup, then follow through with the external source setup in FM. I'm pretty sure it was when I fixed my username and password that it all then worked. One other tip I picked up was to enter for the field "Catalog" when managing external source the name of the external database. Hope this makes sense. Let me know if I can be of any more assistance.

Cheers

Allison

NOTE: My apologies ... I misread your error .. I got a very similar error message but not exactly the same one as you. Not sure if my tip will help.

Edited January 12, 200818 yr by Guest

just a bit of additional information, which may be interest.

If you are also considering using the server to run an import script, it won't work. The script can be run successfully from the local file. However, as the import script step is not web compatible, this (the import step) will not run from a server schedule execution of the script itself. So a server schedule can not be used to run a file script to import ESS (or anything else).

Perhaps try adding the MySQL table to the FM file as an ESS. Manage External Data sources, as an ODBC... then import from the ESS table into an FM table.This works for me.

For testing on local machine this may help:

The Actual ODBC driver and ODBC administrator combination seems a bit flaky, but this is more likely a self induced thing. The Advanced options seems to be the issue. Some back and forth in checking the settings has not always been what might be expected. I may have been misreading my issues with this, however, and it may more be due to the location given in the advance options.

I have used MAMP, and also the MySQL in System preferences, in combinations with Navicat, MySQLAdministrator, and CocoaMySQL, in playing around with MySQL serving, and this has led to problems, which I assume is 2 different server setups. Not something I am on top of at this stage, I readily admit.

Ports 3306 or 8809 used as defaults can be an issue

What is working for me is

MAMP, 3306

and ODBC admin set to:

/Applications/MAMP/tmp/mysql.sock

I haven't seen a filetype message ever.

Hope the former may be of some help.