A way of creating an LOV. Does it achieve something extra than normal way?

Question

Hi,
In some ADF applications I have seen a way of LOV creation where there are two view objects as follows
1. BaseVO having an attribute - 'lovAttribue' and
query as
select '' as lovAttribute from dual;
The only attribute of this VO defines an lov with list data source as LovVO and List attribute as lovItem
2. LovVO having attribute - 'lovItem' and
query as
select lovItem from table where some_condition;
BaseVO is exposed in AM and its data control is dropped on the page to create the LOV.
Another, more common way of creating LOV involves just a single View Object having an attribute which defines an LOV having the List data Source as the same View Object.
I want to know is there any benefit of the first approach for creating LOV?
Regards,
Harmeet K Saini

Answer 1

Thank you for the quick response, varjak.
I did not know about the Thunderbolt option card, so thank you for telling me about that. That would solve a problem if I am getting Apollo Duo, which is a better model of Apollo Twin with more in/out and such. However, I'm only able to afford Apollo Twin right now and it does not come wtih the optional card slot, so unfortunately I would have to pass this option for now.
I would definitely try out the USB monitor adaptor though. It looks like there many company that makes those so I would pick one and see how it works. Too bad my iMac only has USB 2.0, which would be much slower than 3.0 so I would guess there would be lag as you said, but it's worth a try.
Thank you again.
Nao