Strange designer procedure behaviour

Whittall, Conrad Conrad.Whittall@Cognos.COM
Wed, 24 Oct 2001 10:30:05 -0400


Hi Paul,

Just a wild guess, but I think that the database transaction that QUICK
started when the user attempted the (unsuccessful) FIND is probably still
active, i.e. uncommitted.

Assuming you are using the default transaction provided by QUICK (with
Oracle this will be a single transaction called UPDATE) you might like to
try one of the following...

1) Commit or rollback the UPDATE transaction at the start of your DESIGNER
procedure; then start the UPDATE transaction again, do all of your inserts,
then commit the UPDATE transaction at the end of your DESIGNER procedure.

Or...

2) Start a new designer transaction at the beginning of your DESIGNER
procedure, do all of your inserts, commit the designer transaction at the
end of your DESIGNER procedure. Note that this might cause a second attach
to the Oracle database if the default UPDATE transaction is currently active
(which can take some time) as Oracle can only support one active transaction
per attach.

Let us know how you get on.

Best regards,
Conrad

Conrad Whittall
Manager, eLearning Services
Cognos Incorporated, 3755 Riverside Drive, Ottawa, Ontario, K1G 4K9, Canada


-----Original Message-----
From: Paul Howard [mailto:paul@synergy.co.za]
Sent: Wednesday 24 October 2001 05:20
To: powerh-l@lists.swau.edu
Subject: Strange designer procedure behaviour


 

Hello listers,

I have a program that is showing some peculiar behaviour that I am
struggling to understand. Maybe someone can shed some light on it and maybe
suggest a workaround. 

A Quick screen has a named designer procedure which inserts records into an
Oracle table. If the user enters the screen and immediately executes this
procedure everything works as expected. However if the user enters the
screen and does an unsuccessful find and then executes the designer
procedure it seems to go through the motions but nothing is actually
inserted.

I have a feeling that it has something to do with still being in find mode
after the unsuccessful find and that it is not setting altered record for
some reason.

Any ideas? 

Regards

Paul Howard


= = = = = = = = = = = = = = = = = = = = = = = = = = = =
Mailing list: powerh-l@lists.swau.edu
Subscribe: "subscribe" in message body to powerh-l-request@lists.swau.edu
Unsubscribe: "unsubscribe" in message body to
powerh-l-request@lists.swau.edu
http://lists.swau.edu/mailman/listinfo/powerh-l
This list is closed, thus to post to the list you must be a subscriber.

This message may contain privileged and/or confidential information.  If you
have received this e-mail in error or are not the intended recipient, you
may not use, copy, disseminate, or distribute it; do not open any
attachments, delete it immediately from your system and notify the sender by
e-mail promptly that you have done so.  Thank You.