Caution: Apex_Item.Date_Popup and Oracle APEX 3.1

Just to let you know in case you are hitting the following problem or plan to upgrade to 3.1. The version of Apex_Item.Date_Popup which comes with Oracle APEX has a “small” bug. The Date Picker will always write the return value into the first row, independent for which row you have opened the Date Picker.

Carl has already provided a workaround for the bug and I’m pretty sure it will be fixed in the first patchset of Oracle APEX 3.1.

I’m back!

As you may have already noticed, I’m back from my journey to Vietnam and Cambodia. Was a great vacation, liked it alot!

I’m already back since two weeks, but had not much time for blogging or other things. After coming back I almost immediately had to fly to Luxembourg for a project startup meeting of a new Oracle APEX project my company is doing and the nights where used to prepare material for the Advanced Oracle APEX training I did with Dietmar Aust and Denes Kubicek a week later. It paid off to put that effort into it, because we got great feedback from the attendees. More on Dietmar’s blog.

So I hope to find now some time to work on some task which have queued up over the last few weeks. Like a new release of the APEX Builder Plugin (the training attendees liked this tool alot when I showed it to them), a new ApexLib release (it’s really getting time) and I finally should make the switchover from Blogger to my own hosted WordPress installation. Not to forget to write some new blog postings, … So there is a lot to do in the upcoming weeks. 🙂

Using Windows Login Credentials for Single Sign On (NTLM authentication)

Most users are lacy and don’t want to enter login credentials each time they start up an Oracle APEX application. They tell you,

“Hey I have already logged in into my computer, can’t you use that information for the APEX application?”.

Sure we can! The NTLM protocol is one way to do that.

Instructions on how to integrate mod_ntlm have been around for quite some time. See the article on HTMLDB Studio and a more up-to-date version by Martin Köb of GreenIT. But that always involves installing mod_ntlm on your Apache.

Jason Straub, a member of the Oracle APEX development team did some digging and found a PL/SQL only solution which doesn’t require mod_ntlm. Have a look at his first blog posting called “NTLM HTTP Authentication and Application Express” and welcome him as new member of the Oracle APEX blogging community!

Jason, welcome and keep blogging such great articles!

Attention! Are you using the Drop in replacement for V and NV function?

If you are using my Drop in replacement for V and NV function and you are upgrading to Oracle APEX 3.1 then you have to alter the functions to reference the new schema FLOWS_030100!!!

If you are not doing this your applications will not work because the functions are trying to read the session state from the old FLOWS_030000 schema, but there no values can be found for the current session which are stored in FLOWS_030100.

Just to let you know that you are not searching to long why your application doesn’t work after the upgrade.

Note: You may have installed this drop in replacements as optional part of the ApexLib Framework!