Unless someone happened to watch the process, hours or days could pass before anyone noticed this problem. But, in our non-perfect world, sometimes this process failed.Įven though the configuration setting remained checked in the Admin Console, the process simply stopped, and our database no longer would accept incoming connections from the Java app. This process worked seamlessly, as long as FileMaker’s “fmxdbc_listener” process remained active. This required Server Advanced, and enabling ODBC/JDBC in the server settings: The sending application used FileMaker’s client driver, which allowed it to send SQL insert statements to the FileMaker database via FileMaker Server. One of our development projects required enabling ODB/JDBC and sending data via JDBC (Java Database Connectivity). Then leave that floating window open while you work in other windows.Sending data to FileMaker from external sources poses interesting options and challenges. specifying that event::Date is greater than or equal to todays's date but less than or equal to today+5. (Assumes you don't leave the file open and running all the time, that you close out of it at the end of the day and open fresh the next morning).Īnother approach would be to have a small window with a portal to events, anchored by a local calculation field of result type "date" defined as Get(CurrentDate), unstored, and another defined as Get(CurrentDate)+5 also unstored. If you only need it to check once a day, you can do it the same way you would have with FileMaker 6, set a script to run when file is first opened, it does this search, then it won't check again until the next time you reopen the file. You can set it to run every hour or twice a day or however often you want it to check again. That's one method: have that run when you first open the database, and the script it puts on timer does a search for events greater than or equal to today's date and less than or equal to today's date + 5, error capture on, if zero found return focus to the previous frontmost window, otherwise pop up the "found events" window as an alert. After the specified interval has passed, the next time the application is idle, runs the specified script. Runs a specified script at the specified interval.
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |