If you can't find what you are looking for, try searching for it below:
4 Comments
Today a very important Page of an important APEX Application has accidentially been deleted. We didn’t want to step back to yesterdays backup, because right before the deletion many changes took place and we didn’t want to code that again.
Yesterday i stumbled (for the umpteenth time) over the static LOV limitations in Oracle APEX. I tried to have a comma (“,”) in the Return Value which messed up my LOV, because a comma is a seperation character in the LOV definition.
Ever got a “ORA-01841: (full) year must be between -4713 and +9999, and not be 0″ Error when trying to edit an existing user in APEX Administration Panel (Manage Workspaces > Manage Developers and Users) ?
When you create a Form page with the APEX Wizard it puts all the fields in just one column which can create a very long page.
This can reduce the use experience and usability a lot.
Sometimes it is a better way to put the fields in two (maybe three) columns and present them all on one screen. This gives the user the benefit of seeing all the information at once.
Spread the word: SQL Developer 3.0 EA is out AND SQL Developer Datamodeler 3.0 EA is out.
If you missed the latest new: Datamodeler is now FREE (as in “gratis”).
Go get the tools!
Read more about it on Kris Rice Blog
Just a quick note: When you are working with a multilingual/translated APEX Application you sometimes need to join LOV Values in your SELECT Statement.
APEX 4.0 comes with tons of new Features, a good summary can be found in the New Feature Description Application.