14:15:51 ERROR Job Launcher:91 - Traceback (most recent call last): 14:15:50 INFO m.e.d.o.OracleMetadataEtl:36 - In Oracle metadata ETL, launch extract jython scripts In addition to enabling ODBC in the FileMaker Server Admin tool, the privilege set you are working with needs to have the access via ODBC extended privilege enabled.14:15:50 INFO m.e.d.o.OracleMetadataEtl:178 - PySystem path: For the remainder of this post, I’m going to limit myself to talking about FileMaker Server. If you are working with a standalone database, you can only connect from RazorSQL to your solution on the same machine. RazorSQL connects to FileMaker via the ODBC interface, so you have to have that enabled in your standalone solution or FileMaker Server. Once you have your query perfected in RazorSQL, you can then build it in FileMaker, knowing that you have the basic query correct. With regard to the last issue, RazorSQL is a nice tool for working directly with your FileMaker solution to very quickly test SQL code.

On the down side, you have to be very careful about its impact on your application’s performance and building SQL queries in FileMaker’s calculation dialog is challenging.

It can help keep your relationship graph simpler, allow you to query data without changing your context, and makes virtual lists easier to build among other things. The advantages and disadvantages of SQL in FileMaker are pretty well known. In the early days it required a 3rd party plugin, but since version 12 we’ve been able to run SQL Select statements against our FileMaker data with the native Execute SQL function. Developer’s have been able to run SQL queries against their FileMaker data for many years.

Razorsql characterconverterogs