'Cancel' and 'OK' buttons in the LOV screen switch places randomly

Hi!
While running Oracle Forms and invoking the LOV ,'Cancel'
and 'OK' buttons in the LOV screen switch places randomly.Has
anyone encountered this before? Is there a way to fix this.
Thanks in advance.

I know that the find/ok/cancel button order is different between
running in client/server and on the web.
Are you testing your form both ways and seeing the different
order or are you running into something different?
Candace Stover
Forms Product Management
Oracle Corporation

Similar Messages

Maybe you are looking for

  • Crystal Reports Server 2008 dispose not closing document

    Hey everyone, I;m running some reports through Crystal reports 2008 server (no service packs) using the RAS sdk and Java. This was working swimmingly for a while until yesterday when the server hosting the RAS and app server fell over. I tracked it d

  • Is there a way to control the video's speed in VideoDisplay?

    What I actually planned was to create a slow-mo feature on my players. Basically, reducing the movie speed by half (or by .25X the actual speed). Video's are on SWF format. Is there a way to do it? Thanks in advance. Any help would be appreciated.

  • Download itunes 12.0.1 and now it wont let me sync

    Download new itunes update and now it wont let me sync. Keeps saying I need 26gb of free space which it didn't say before I downloaded the update. It doesn't make sense. It keeps saying: The iPod cannot be synced because there is not enough free spac

  • Active state not working in scrolling site (with anchor links)

    I'm design a scrolling site with anchor links and an horizontal menu on the top. when i publish the site and click on the menu buttons the site scrolling to the place of the anchor but the active state in the menu is not working. now... when i leave

  • JDBC: send batch of SQL commands as anonymous PL/SQL block

    Hi All, I did a little measurement to see if I can improve jdbc applications by batching dissimilar SQL commands into one anonymous PL/SQL block and execute it once. To my surprise, for a batch of 5 SQL commands, it take 60% more time than execute ea