Do you want to learn more about Oracle APEX and get some insights into Oracle APEX 3.2?

Then you have to attend our second Oracle APEX training! This time it's held in Munich from 02-Jun-2008 to 04-Jun-2008.

More detailed information follows in German:

Denes Kubicek, Dietmar Aust und ich freuen uns Euch wieder ein paar neue Einsichten, Tipps und Tricks zu Oracle Application Express (APEX) vermitteln zu dürfen. Die Agenda der Themen welche wir behandeln gibt es hier.

Besonders freut es mich, dass wir dieses Mal den Marc Swetz vom Oracle APEX Entwicklungsteam aus den USA als Gastredner begrüssen dürfen!

Marc wird uns ein paar Einblicke in die nächste Version von Oracle APEX und dem SQL Developer geben. Er wird auch an den Abendlichen Q & A Sessions teilnehmen, damit er aus erster Hand die Fragen und Anregungen die bei der täglichen APEX Entwicklung auftauchen, aufnehmen kann. Nutzt diese ideale Gelegenheit um Euch mal mit dem Oracle APEX Entwicklungsteam auszutauschen! Und keine Angst, der Marc spricht Deutsch :-)

Die Abendlichen Q & A Sessions sind überhaupt beim ersten Training sehr gut angekommen, weil es die Gelegenheit ist seine konkreten Projektfragen/-Probleme von drei Oracle APEX Experten beantworten zu lassen.

Also nicht lange zögern sondern jetzt Anmelden!

Würde mich freuen Euch dort zu sehen.

« ... Read full posting ... »

Undocumented option for Static List of Values

Did you know that the STATIC and STATIC2 keyword used to define Static List of Values for Oracle Application Express (APEX) contains an undocumented option?

The online help documents the usage with

STATIC[2]:Display Value[;Return Value],Display Value[;Return Value]

But what to do if one of your values contains the semi colon or the comma in the text? You will get a problem with the predefined separators!

In such a case you can use

STATIC[2](lov-entries-sep,display-return-sep):Display Value[<display-return-sep>Return Value]
<lov-entries-sep>Display Value[<display-return-sep>Return Value]

For example:

STATIC2(~,*):Cat, Dog*1~Nemo, Shark*2

« ... Read full posting ... »

Is there life on planet Oracle APEX 3.2?

Sure there is! ;-)

David Peake the Product Manager for Oracle Application Express (APEX) recently blogged about this "unofficial" insight what's on the drawing board after the patch release for Oracle APEX 3.1.

Get the details in this A peek over the Application Express horizon posting!

« ... Read full posting ... »

Remote debugging of an Oracle APEX application

If you ever wanted to remote debug the PL/SQL code which is called during execution of an Oracle APEX application, then have a look at the May/June issue of the Oracle Magazine. David Peake wrote an article titled The Power of Two on how to use SQL Developer to do that. On the German Oracle APEX Community Web-Site you will find a similar how-to in German.

Update: In Oracle APEX 3.1.1 there will be a new debug mode called REMOTE to enable remove debugging in Oracle APEX without having to modify the application. See the related posting on the OTN Forum.

« ... Read full posting ... »

Oracle APEX: Got a 404 Not Found?

Maybe you also already got the 404 Not Found error message

The requested URL /pls/apex/wwv_flow.accept was not found on this server.

when you submit an Oracle APEX page, ...

There are a lot of reasons why this error can occur. But the above error message doesn't tell you a lot about the root cause of the problem. The real error message can be found on your Apache Web server in the Apache\Apache\logs\error_log.xxxxx file. There you will find and entry like

[Thu Apr  3 ...] mod_plsql: /pls/htmldb/wwv_flow.accept HTTP-404
wwv_flow.accept: SIGNATURE (parameter names) MISMATCH
VARIABLES IN FORM NOT IN PROCEDURE: P_T02XXX
NON-DEFAULT VARIABLES IN PROCEDURE NOT IN FORM:

Without the above information, you have no chance to find out what's causing the 404 error. But the problem is, that most developers don't have access to the application server.

You don't have to!

Just put

<Location /pls/apex>
 ...
 PlsqlErrorStyle  DebugStyle
 ...

into your dads.conf/marvel.conf and after restarting the Apache server you will get the error message directly in your browser.

For more details about PlsqlErrorStyle, have a look at the documentation.

Note: Only use this setting on developments systems, because on production systems a hacker might get more information as he should!

Credit for this tip goes to Dietmar Aust!

« ... Read full posting ... »