Skip to main content

Can't wait to unpack my ACE Award...

Last Friday I received an email from the Oracle ACE Program Office that I am accepted for the Oracle ACE Award! At this moment I am not on the ACE Directory and also my OTN Forum Profile doesn't show the Ace of Spades yet, but that should be fixed in a few days or so (I am more than thrilled to swap my two 'Guru medals' for one spade thing). The award itself seems a little dangerous because I had to sign a document to release Oracle from all liability for any injuries caused by that award. Seems like a rather sharp thing...
According to the ACE Directory I am the 215th worldwide, 13th in The Netherlands, and, after Andrew and Piet, the third within Logica.
A special thanks to David and John who nominated me. I guess I owe them a few drinks during the upcoming ODTUG event...

Comments

Patrick Wolf said…
Congratulations!

Patrick
Byte64 said…
Great achievement Roel!

Congrats
Flavio
Unknown said…
Congratulations - Well Deserved

Your contribution to the APEX community is very much appreciated.

David
Monty Latiolais said…
Roel,

Awesome news! Great to see your efforts recognized in this fashion.

Monty
Louis-Guillaume said…
Congrats!
This is good news.

Louis-Guillaume
Martin D'Souza said…
Congrats!

Martin
Marco Gralike said…
Don't forget to check in the OOW "Dutch ACE House"

Forms geek ;-)

Sorry, Congrats of course !!!
Unknown said…
Congratulations !

Francis.
Gerben said…
Congratulations!

Well done!

Gerben
Congratulations. Lucky 13 ? :-)
Joel R. Kallman said…
Congratulations, Roel! As David said - it is very well deserved. I am personally grateful for all of your contributions to the Oracle APEX community.

Joel
Anonymous said…
Congratulations.

Groet,

Yuri
Roel said…
Thanks gents for all your nice comments!
Roel
Paulo Vale said…
Roel,

Congratulations on your award. The APEX community appreciates your efforts and the prize is well awarded.

When I grow up, I want to be like you :D

Popular posts from this blog

apex_application.g_f0x array processing in Oracle 12

If you created your own "updatable reports" or your custom version of tabular forms in Oracle Application Express, you'll end up with a query that looks similar to this one: then you disable the " Escape special characters " property and the result is an updatable multirecord form. That was easy, right? But now we need to process the changes in the Ename column when the form is submitted, but only if the checkbox is checked. All the columns are submitted as separated arrays, named apex_application.g_f0x - where the "x" is the value of the "p_idx" parameter you specified in the apex_item calls. So we have apex_application.g_f01, g_f02 and g_f03. But then you discover APEX has the oddity that the "checkbox" array only contains values for the checked rows. Thus if you just check "Jones", the length of g_f02 is 1 and it contains only the empno of Jones - while the other two arrays will contain all (14) rows. So for

Filtering in the APEX Interactive Grid

Remember Oracle Forms? One of the nice features of Forms was the use of GLOBAL items. More or less comparable to Application Items in APEX. These GLOBALS where often used to pre-query data. For example you queried Employee 200 in Form A, then opened Form B and on opening that Form the Employee field is filled with that (GLOBAL) value of 200 and the query was executed. So without additional keys strokes or entering data, when switching to another Form a user would immediately see the data in the same context. And they loved that. In APEX you can create a similar experience using Application Items (or an Item on the Global Page) for Classic Reports (by setting a Default Value to a Search Item) and Interactive Reports (using the  APEX_IR.ADD_FILTER  procedure). But what about the Interactive Grid? There is no APEX_IG package ... so the first thing we have to figure out is how can we set a filter programmatically? Start with creating an Interactive Grid based upon the good old Employ

Stop using validations for checking constraints !

 If you run your APEX application - like a Form based on the EMP table - and test if you can change the value of Department to something else then the standard values of 10, 20, 30 or 40, you'll get a nice error message like this: But it isn't really nice, is it? So what do a lot of developers do? They create a validation (just) in order to show a nicer, better worded, error message like "This is not a valid department".  And what you then just did is writing code twice : Once in the database as a (foreign key) check constraint and once as a sql statement in your validation. And we all know : writing code twice is usually not a good idea - and executing the same query twice is not enhancing your performance! So how can we transform that ugly error message into something nice? By combining two APEX features: the Error Handling Function and the Text Messages! Start with copying the example of an Error Handling Function from the APEX documentation. Create this function