Basically the final solution I need is to be able to write to the database without having the DARN FileMaker Pro application open. Descripti onĪny help is greatly appreciated. StrSQL = 'INSERT INTO Test2003 (TestField1) VALUES ('please insert')'ĭebug.Print (intInc).

StrCnn = 'DSN=FileMakerTestA' 'dsn used - FileMaker Pro ODBC driver Here is the VBA code which produced the above two errors in the immediate window: Optional feature not implemented.ĭriver's SQLSetConnectAttr failed. When run, the ADO connection object's error collection holds the following two items after opening a connection: Sharing of the FileMaker Pro files is set correctly. I am logged in as the local admin, and the service is started as this local admin.

However, when run as a service, the same code does not write to the database. Now it runs as a service in the background. So, I decided to make the FileMaker Pro run as a service (using SVRANY.exe and INSTSVR.exe, and making the proper registry entries). The web guys understandably do not want an open application on their web server. They're using ASP, and so I figured out how to write to FileMaker Pro with FileMaker's ODBC driver, and can insert records successfully through VB Script, but determined that you can't connect to the database (with ADO) unless the FileMaker Pro client is up and running as an application!! Sounds awful already. I'm a database developer/DBA (Oracle and some SQL server) and, being the new guy at our company, last week I was given the task of figuring out how to write to the FileMaker Pro database for the web guys here.

Filemaker pro database