Warning: Declaration of My_Walker::start_el(&$output, $item, $depth, $args) should be compatible with Walker_Nav_Menu::start_el(&$output, $item, $depth = 0, $args = NULL, $id = 0) in /home/dbhqne5/public_html/wp-content/themes/creativesans/include/misc/nav.php on line 31 dbhq.netDevelopment Archives - dbhq.net
The new Script Workspace in FileMaker Pro 14 delivers on some long-asked for developer features, like color coding, more keyboard access, and a unified interface. But like any new feature, it’ll take some getting used to before you’re fluent with the new workflow. Here are some tips for ...
Appropriate feedback is critical to creating a good user experience. But was does “appropriate” mean? It’s a given that you need to let users know when an error occurs. Sometimes appropriate feedback tells them that everything’s just fine, for example “Results: 17 invoi...
Much of what happens behind the scenes of your scripts is, and should be, invisible to your users. But there are times when you need to give feedback about what’s happening. If a script can’t process an invoice, or is finished marking a found set of records, it’s common to use a Sh...
A common complaint about FileMaker (https://www.geistinteractive.com/2014/04/07/top-feature-request-filemaker-14/) is the lack of a native method to pass multiple parameters to a script. Many developers have tackled this problem using different methods, including include Word Count, Value Count, del...
When we provide instructions for creating a custom function, we will specifically provide any Parameters which need to be defined, and also provide the code for the function. The code will be indicated with the following beginning/ending indicators: ———–BEGIN CODE—̵...
No matter what type of database you’re creating, at some point you’re going to find an occasion to employ some sort of method to let your user know they have made an error or neglected to fill in a required value. One method of achieving this goal is through the use of a custom dialog. [...