actually the drop in replacement for V, NV and DV where just to fix the deterministic problem. In my ApexLib framework I have implemented ApexLib_Item.NV and ApexLib_Item.DV which are taking care of that.

Regards
Patrick

Sorry to comment on such an old post, but I just got burned by the nv() function, and noticed that your version here has the same (potential) issue. It’s basically the same issue noted by Lev on the dv() function–nv() doesn’t pay attention to format masks. So if a number has a grouping separator, nv() throws an invalid number error. I posted a solution to this using the apex dictionary to get the proper format mask on my blog.

-David

you are right, I have added an optional p_format_mask parameter.

But anyway, it’s better to use the ApexLib function ApexLib_Item.DV, because it automatically knows which format mask has to be used for the conversion.

Thanks for your suggestion
Patrick

Lev

I’m not so familiar with database links, especially if different version are involved. I’m not sure which optimizer (on which db) is responsible. I think the 9.2 one is asked at least for one part of the query (his tables), because only he can has the statistics and can decide what is the best explain plan.

Be on the save side in that case and use

SELECT * FROM ORA92_TABLE WHERE ID = (SELECT V(‘APEX_ITEM_VALUE’) FROM DUAL);

That always works, with all DB versions!

Which “check images” do you mean?

Patrick

In view on 10g side there is call like:

select * from ora92_table
where id = v(‘APEX_ITEM_VALUE’)

What is fancy that saving that query in Apex, creates loooong query …

This is just a small add to 10g2 deterministic function which should solve the problem of that…looks like the problems still remains …

Just my proved 2 c!

P.S.
BTW, how do you generate these “check images”? THX

thanks for the info. Don’t know what’s going wrong here.

Added the content of the script to the posting.

Thanks
Patrick