How do I save current record displayed with a Rbasic Routine (AREV Specific) [Revelation On-Line Wiki]

AREV Specific

Sign up on the Revelation Software website to have access to the most current content, and to be able to ask questions and get answers from the Revelation community

At 04 OCT 2001 04:35:23PM Bob Laqua wrote:

My old Arev v1.16 routines are failing in v3.12.. anyone surprised ;)

From a window I want to send the current record displayed

to the Forms Processor for Printing.

However if the current record is a new record with data that was

just entered or the current record has been updated with new Data, including the current prompt, then I would need to save this record

first before sending it to the Forms processor for printing.

I've assigned under softkey for the window Shift-F10 to run a Dict

Formula that Test the Record & Prints the Form.

* check if current prompt has changed

* issue carriage return so input pattern check will happen

* only problem is potential endless loop

FMC.NO=WC_W%(WC_WI%)

IF WC_IS% @RECORD THEN
 @DATA=CHAR(13)
 CALL CATALYST("F","SF10")
 GOTO NEED.SAVE
END

* check for required prompts

* CODE NEEDED HERE

!

* if the record is new or it has changed then

* file the record like using F9 so all prompt checks are done

* then bring record back (with out changing current browse list)

* then re-issue SF10 to start printing process again.

* CODE NEEDED HERE

!

* I've tried using

* WC_SAVE_REC%=1 & WC_RESET%=5

* But got weird results.. haven't figured the correct combination of use.

NEEDS.SAVE:

END

Any Ideas ?

Thanks

At 05 OCT 2001 10:23AM Aaron Kaplan wrote:

At 05 OCT 2001 10:31AM [url=http://www.sprezzatura.com" onMouseOver=window.status=Click here to visit our web site?';return(true)]The Sprezzatura Group[/url] wrote:

grr….Opera has some serious problems with this site…oh well.

I would have just had the system do a
Write @RECORD to Wc_Src_File%, @ID
to update the record. No messing about with browse lists or screen refreshing or anything.

Making changes to Window Common variables will not take affect until the WINDOW program is re-entered. From what I can see in your program, this won't happen.

The Sprezzatura Group

World Leaders in all things RevSoft

At 05 OCT 2001 01:42PM Warren wrote:

Having experienced major problems like this when upgrading a client system from 1.16 to 2.0x ages ago I found you often had to save @RECORD, @ID, and @DICT prior to making a CATALYST call from Windows and restore them after the call. I suppose you could do a PUSH/POP.SESSION.

But why not do as Aaron suggests (and I posted earlier prior to reading this thread) and write @record directly?

View this thread on the forum...