Bill Doerrfeld
-
Posts
6 -
Joined
-
Last visited
Everything posted by Bill Doerrfeld
-
Multiple Where conditions in ExecuteSQL
Bill Doerrfeld replied to Bill Doerrfeld's topic in FileMaker Query Language or FQL
Nevermind. Went out for a short walk and the answer came to me which is... ExecuteSQL( " SELECT COUNT ( ID ) FROM Item WHERE Due = ? AND Status = ? " ; "" ; "" ; Get(CurrentDate) ; "Active" ) -
I'd like to use ExecuteSQL to get a count on all records due today whose "Status" is not "Active". The following code returns the count on all records due today. How do I add an additional WHERE condition for Status != Active? ExecuteSQL( " SELECT COUNT ( ID ) FROM ExecuteSQL WHERE DueDate = ? " ; "" ; "" ; Get(CurrentDate) ) I know how to achieve this with "standard" SQL but am stumbling with this ExecuteSQL implementation. Thanks.
-
There's really no advantage in performance. In fact, in some areas of the UI performance is slower. For some metrics on this, check out the "performance tag" in my blog at www.billonfilemaker.com. There are other advantages brought with the move to Cocoa. Speed really isn't one of them (at least from the UI side).
-
I haven't looked closely at the XML libraries with SM, but, I didn't see any mention of Xpath. Is there a way to use an existing jar file with SM for Xpath support? Anyone gone this route yet with pointers on exactly what to do?
-
Regarding #2, no big deal, I have a workaround in my script for handling the null.
-
1) When the popup menu is clicked on, the entire screen dims slightly until the popup value is selected. Is there a way to prevent the dimming? 2) Once the popup menu is "popped up" if the use clicks outside of the menu a null value is sent and the popup is closed. This is quite annoying. Nothing should be sent. Is there a way around this?