Showing posts from August, 2012

APEX Tabular Form: focus cursor on first element of new row

Tags van Technorati: apex , dynamic action , tabular form , add row , focus , cursor I just got the question from a fellow developer, how to focus the cursor to the first input field of a newly added row using the ADD button in a standard APEX Tabular Form. Actually, I would expect APEX to do this automagically. But it doesn’t. To implement this behavior is actually really simple.     For this example I create a simple tabular form based on the demo_customers table: This is what the form looks like when you click the “Add Row” button. As you can see, none of the input field has focus at this time. To focus the cursor on the first field of the new row (Cust First Name), I somehow have to change the behavior of the “Add Row” button. Let’s have a look at it’s definition: The click-action of the button is actually a JavaScript call: addRow();. Naturally I want to keep this action, but after this, I want to start an additional action that should set the focus to the input field. To

Running Standalone APEX Listener as Windows Service

When working with APEX you certainly want to use the APEX Listener. It’s a great piece of software and Oracle is committed to extend its functionality (Oracle recently release the beta version of the new APEX Listener 2.0 ). When installing the APEX Listener, you basically have two choices: run APEX Listener “Standalone” deploy the Listeners WAR file to one of the supported webservers The problem (at least, my problem): when using the APEX Listener on my laptop/desktop with my local APEX instance, I do not want to set up a whole webserver, just to be able to develop APEX applications. So I,’m choosing the lightweight option: Standalone! But the annoying thing about the standalone installation is, that I have to start the APEX Listener from the command line each time I want it to be available. It just would be so much easier to just have it as a Windows service, stating during system boot. Seems that an APEX developer from Poland, Andrzej Nowakowski , solved this problem for us and