Using LOV's in query-only mode
Date: 1997/06/23
Message-ID: <33AF02B7.B2546612_at_mystical.net>#1/1
[Quoted] I'm really stuck! Please help.
I've made a F45 form with a text item that can call a LOV to populate itself with a number corresponding to a subdivision name in another table -- you pick the sub name from the list, and the form populates the field with a representative number. It's all in query-only mode to this point. The record group for the LOV is created by
SELECT lu_name, lu_num
INTO :lu_name, :asr_sub_number --(f.k. to lu_num - represents subdiv
name)
FROM lu_subs;
This all works fine - remember it's a query-only form - set at the block properties level. The problem is, after you retrieve the LOV, pick one, and execute the query, it populates the all the fields from the first row of the queried group, then as the form leaves "query-only' mode after the query it displays "Would you like to Commit to the changes you have made?" I didn't change anything! Tell it "No" and everything is fine.
I don't understand why this message appears - if you do tell it "Yes," to commit, it returns an error saying it can't insert record -- which is logical as the form is restricted from inserting, updating, or deleting in the block properties. After that it will continue to show this "Would you like to Commit" message until I finally tell it "No."
How can I suppress this message? I'm guessing since I opened an implicit cursor with the select into, that it assumes something was changed. I can't rollback because Forms treats that as a clear_form -- and I would lose all my queried info. I don't want to commit to nothing either - simply out of principle if nothing else!
TIA,
-Ian
Received on Mon Jun 23 1997 - 00:00:00 CEST