Execute SQL, I believe, doesn't return any SELECT results. You can insert, update or delete based on the examples in the help menu. So that's not what you are looking for.
I think what you are looking for is an ESS table not a script step. So, first add your MySQL database to the system DNS. Then add the database to your FileMaker file by going to File > Manage > External Data Source. Then open Manage > Database and go to the Relationships and add a table occurrence for your MySQL table you want to pull data from. Since it now acts like a FileMaker Table Occurrence you can now script your query just like it was any other table and pull the results you are looking for.
thanks for the clarification. This sums it up pretty well. If I want to or not, I'm forced to stick whatever FileMaker has to offer.
I still can't imagine how can someone seriously consider to suppress the result from *the* most used sql command?
Thank you very much,
The hardest concept from the transition from the SQL world to FileMaker is not understanding that FileMaker is context sensitive. A layout is based on a table occurrence, which is based on a table. Results of a "found set" can be brought out via a layout. Again you must keep in mind that it is context sensitive.
There is no direct results only per se as in the SQL world which just has a returned results with no attachments. If you can grasp this concept then Execute SQL not having SELECT should make sense.
Now in FileMaker there is an option to Import via ODBC and import that into an existing or new table.