OraFAQ Forum: Forms » prevent commit after execute

Home » Developer & Programmer » Forms » prevent commit after execute_query (forms 6i)

Show: Today's Messages :: Polls :: Message Navigator
E-mail to friend

prevent commit after execute_query [message #393845]

Tue, 24 March 2009 11:12

deahayes3
Messages: 203
Registered: May 2006

Senior Member

Hi all,

I am using the following to search for a record, but before the record is viewable it always ask me "Do you want to save changes you have made", I hit "no" and the record shows. How can I stop this message from displaying?

Code used:
set_block_property('FIND_INC_RECORDS',default_where,'PERSON_ID = '||chr(39)||:FIND_INC_RECORDS.PERSON_ID||chr(39));
Go_block('FIND_INC_RECORDS');

execute_query;

Report message to a moderator

Re: prevent commit after execute_query [message #393847 is a reply to message #393845]

Tue, 24 March 2009 11:15

cookiemonster
Messages: 13938
Registered: September 2008
Location: Rainy Manchester

Senior Member

I assume you're not going into enter-query mode before assigning a value to :FIND_INC_RECORDS.PERSON_ID?

Report message to a moderator

Re: prevent commit after execute_query [message #393848 is a reply to message #393847]

Tue, 24 March 2009 11:22

deahayes3
Messages: 203
Registered: May 2006

Senior Member

No, should I?

Report message to a moderator

Re: prevent commit after execute_query [message #393850 is a reply to message #393845]

Tue, 24 March 2009 11:31

cookiemonster
Messages: 13938
Registered: September 2008
Location: Rainy Manchester

Senior Member

That's the standard way of querying records.
You shouldn't need to mess around with default_where then.

Basically you're setting a value to use in a query, but because you're not in enter-query mode forms doesn't know that is what your doing and it assumes you're trying to create a new record.
Hence it asks you if you want to save the changes you made.

Always use forms default behaviour unless it really doesn't work for your requirements.

Report message to a moderator

Re: prevent commit after execute_query [message #393851 is a reply to message #393850]

Tue, 24 March 2009 11:34

deahayes3
Messages: 203
Registered: May 2006

Senior Member

ok, thanks.

So how would enter_query work to pull record based on the person_id?

Report message to a moderator

Re: prevent commit after execute_query [message #393852 is a reply to message #393845]

Tue, 24 March 2009 12:09

cookiemonster
Messages: 13938
Registered: September 2008
Location: Rainy Manchester

Senior Member

enter_query

enter value in person_id field

execute_query

Report message to a moderator

Re: prevent commit after execute_query [message #393854 is a reply to message #393852]

Tue, 24 March 2009 13:14

deahayes3
Messages: 203
Registered: May 2006

Senior Member

Thanks for the response, but it is still asking me to save.

I have.....

go_block('find_inc_records');
enter_query;
--person_id is copied to field in this block from a LOV execute_query;

Its now taking even longer to execute.

Report message to a moderator

Re: prevent commit after execute_query [message #393875 is a reply to message #393845]

Tue, 24 March 2009 15:07

cookiemonster
Messages: 13938
Registered: September 2008
Location: Rainy Manchester

Senior Member

Presumably it's now asking when you do enter_query.

There's some code that's changing the record status to insert, you need to find it and remove it.

Report message to a moderator

Previous Topic:	Thumb Scanner with forms
Next Topic:	CLEAR THE LIST ITEM

Goto Forum:

-=] Back to Top [=-

[ Syndicate this forum (XML) ] [

]

Current Time: Fri Sep 20 14:33:17 CDT 2024