Presentation time!

I just came back from holiday and found not less than four (4!) invitations to present in my mailbox. The first one contained the good news that my suggested session for Oracle Open World got accepted! A big thank you to all who voted on Oracle Mix!
The second one was a 'Dutch OOW Preview Session' at AMIS (on 11th September) where a lot of Dutch OOW presenters will give a sneak preview of their sessions for the Dutch audience. A good time for a final practice!
The third one was the acceptance of my abstract for this years UKOUG, from 1st to 5th December, in Birmingham, which is great because I really do like this conference.
And finally the last one is Logica's PRO4PRO, probably somewhere in October, where my colleague Rutger and I will do a presentation with the catchy title "Extreme RAD : Live Web Application Development with Oracle Application Express". During this session we will build a web application from scratch....I know it is risky but should be a lot of fun!

So now it's about time to finalize and polish up my presentations and practice my presentation skills!

Comments

Dan McGhan said…

Roel,

Congratulations! Keep spreading the gospel ;)

Regards,
Dan

3:16 pm

Monty Latiolais said…

Roel,

It's great to see your work starting to receive its due.

Monty

5:08 am

Refresh selected row(s) in an Interactive Grid

In my previous post I blogged about pushing changed rows from the dabatase into an Interactive Grid . The use case I'll cover right here is probably more common - and therefore more useful! Until we had the IG, we showed the data in a report (Interactive or Classic). Changes to the data where made by popping up a form page, making changes, saving and refreshing the report upon closing the dialog. Or by clicking an icon / button / link in your report that makes some changes to the data (like changing a status) and ... refresh the report. That all works fine, but the downsides are: The whole dataset is returned from the server to the client - again and again. And if your pagination size is large, that does lead to more and more network traffic, more interpretation by the browser and more waiting time for the end user. The "current record" might be out of focus after the refresh, especially by larger pagination sizes, as the first rows will be shown. Or (even wors...

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 ...

Caution when using Suppress Change Event on an Interactive Grid Column

There are some, maybe rare, use case when you want to set the " Suppress Change Event " switch of a Dynamic Action to " Yes ". Usually that's only necessary when the Dynamic Action is fired On Change and executes a Set Value with the same field as a target. There might be a chain of events leading to this or just one. If you forget to set it you'll end up in an endless loop and your browser will choke. That works all fine and as expected with regular Page Items. However ... when you apply this to a column in an Interactive Grid something unexpected happens. When you set the Suppress Change Event of a Dynamic Action that fires on change of a column to Yes , the value of that item seems empty when you leave that field (column)! If you navigate back into that field, the (new) value does show up... You can call it a feature, you can call it a bug, but bottom line it is unexpected and undesired behaviour. The solution is to call the Grid method SetActiv...

Roels Blog

Search This Blog