SQL analytics can be used to generate break columns in your queries, without the need for break formatting attributes in APEX or the old fashioned break on option in SQL*Plus.
I came across an example recently where I wanted to apply the break formatting in my query to avoid extra sub-totals from being displayed after each break.
Truth be told, the default "no data found" message for APEX reports is pretty boring.
My experience patching Oracle APEX v4.2.1 to 4.2.3 on my Windows 7 laptop.
Personally my main driver for this is to experience the updated themes and templates. I'd also like to explore the packaged applications and see if any of the dynamic PL/SQL regions have been converted to templates.
I already had 4.2.1 installed and before the patch was available to me I thought I'd try running scripts on the full download of 4.2.3
It turns out if you attempt the apxpatch.sql script you get
I'm not a huge user of Firefox anymore. My exodus from IE brought me to Firefox, but then Chrome came along and I've been happy ever since.
That's quite analogous to my mobile telephone experience - starting with Nokia, big jump to first generation iPhone, now happy with Android.
This post was inspired by a question on the OTN APEX forum, which contains requests for two fairly common scenarios:
1) A select list dependent on another select list
2) A report the updates based on the selections.
The original post submitted the page after each select change - APEX 4.x makes this unnecessaary thanks to cascading select lists.
I've re-posted my comment here because they were thoughts rattling in my brain that I was going to rabble on about one day.
Quite a few times I see a questions regarding how to share authentication between Oracle APEX applications so the user does not need to log in a second time.
As long as your link between the applications share the session ID, the solution is simple - set the cookie name the same across your applications.