@ATTACK - @Modal
Referential Integrity
Reader's Clinic - Related Windows
Window or Not ?
Vroom - Window Processing
QTIPS - Window Symbol Tables
VROOM - Window Processing II
@ATTACK - @HW
Uncommon Knowledge - WC_Reset%
Reader's Clinic - Related Windows
Window or Not?
Reader's Clinic - Scribe Replace Processes in Window
Soft Windows
QTIPS - Window Bug and Debugging Window Bug
Overlapping Windows And Window Menus
QTIPS - New Catalyst Option
QTIPS - Collectors on the fly
QTIPS - Blank Menus in Windows
QTIPS - Moving Objects the EASY way.
Reader's Clinic - Screen Width
Screen Grabber
Reader's Clinic - Slow Multivalued Screen Display
Utility Diskette # 4
SecureUser
VERBatim - V86
Advanced Revelation Initialisation Sequence (Overview) by Mike Pope
@ATTACK - @Record
@ATTACK - @Reduction.Done
Collector Windows
Soft Windows
Reader's Clinic - Template Name at Pre-Init
RTP Series - RTP50
@ATTACK - @Messages
Advanced Revelation Initialisation Sequence (Overview) by Mike Pope
Caching in on the Frames Array - Mike Pope
SecureUser
VERBatim - V25
@ATTACK - @Files.System
Advanced Revelation Initialisation Sequence (Overview) by Mike Pope
REVMEDIA Revisted
Networked %SK%
RTP Series - RTP25
A RevTechie Replies - And Miscellaneous Jottings - Mike Pope - Revelation Technologies (UK) Ltd
QTIPS - DOS File Names
DOS Interfacing (Part II)
VERBatim - V116
@ATTACK - @Pri.File
@ATTACK - @Rollout.File
File Variables
How Indexes Are Updated
Index Record Layouts
QTIPS - File Variable of File In SELECT Statement
QTIPS - Amending non-Attached Files
LINEAR HASH FILE STRUCTURES - Part 1
Index Flush
QTIPS - File Handle Structure
@ATTACK - @File.Error
@ATTACK - @Rn.Counter
Reader's Clinic - Related Windows
Reader's Clinic - Fixing %Windows% Using Depend.Update
QTIPS - Updating Indexes
How Indexes Are Updated
REVMEDIA Revisted
QTIPS - Improving the LH_VERIFY Window
VERBatim - V17
VERBatim - V6
VERBatim - V125
Utility Diskette # 3 - Part I
Version 3 Technical Highlights - Copying Rows Programmatically
Version 3 TCL Subroutines - Copying Rows
Playing with Scan Codes
QTIPS - Compiling Protection Code
QTIPS - Invalid Code and Command
QTIPS - Code/Command Help
Compiling 64K on a Shoestring by Blaise Wrenn (LexStat Systems Ltd)
QTIPS - Command Line Options
QTIPS - Invalid Code and Command
QTIPS - Code/Command Help
Utility Diskette # 4
RTP Series - RTP27
QTIPS - Printing Large Variables from the Debugger
VERBatim - V87
Redisplaying Multi-Values
Uncommon Knowledge - WC_Browse_Next%
Uncommon Knowledge - WC_Reset%
Reader's Clinic - Related Windows
Uncommon Knowledge - WC_Amv_Action%
Uncommon Knowledge - WC_Valid%
QTIPS - Window Bug and Debugging Window Bug
REVMEDIA Revisted
Uncommon Knowledge - WC_Reset%
DOS Interfacing (Part II)
Reader's Clinic - Preventing Records Being Amended
How Indexes Are Updated
A RevTechie Replies - And Miscellaneous Jottings - Mike Pope - Revelation Technologies (UK) Ltd
Caching in on the Frames Array - Mike Pope
Reader's Clinic - Preventing Records Being Amended
QTIPS - Finding/Replacing Spaces With The Editor
Reader's Clinic - Scribe Replace Processes in Window
Vroom
RTP Series - RTP32
Utility Diskette # 3 - Part I
Reader's Clinic - Page Marks in Windows

RevMedia FKB

DocumentV2I9A1
TitleReader's Clinic - Related Windows
KeywordsRELATED
WINDOW
RELATER
WC_DISPLAY_ACTION%
WC_RESET%
STATUS()
TextSeveral readers have asked "When I call a related window FROM my current
window to add related records is it possible to have my CURRENT window
reflect these changes when it returns?"

In the classic customer/invoice EXAMPLE the invoice window might be a
related window FROM the customer screen The user might be able to softkey
to the invoice window add another invoice and then return to the customer
window Under these circumstances @RECORD contains the linking IDs and
being in memory is not updated

Note that the system routine responsible for updating related indexes
(RELATER) checks to see if the lock set on the file to be updated is that of
the CURRENT workstation (i e STATUS() is set to 1) If so the lock is
ignored and the update takes place regardless This is because when a record
is written to disk SI MFS reads the old record in and ensures that any
protected fields (as "related to" fields would be) are the same as the disk
copy If not they are changed to reflect the disk copy

Thus on the post window code and command option for a related window a call
to a commuter program that simply reread the new values and inserted them
into @RECORD could be used If the values were displayed on screen
WC_DISPLAY ACTION% and WC_RESET% would ALSO need to be set to redisplay the
new values E g

POST_REL_SHIFT_F1:
* We already have lock so just ignore it and continue WITH the read
READ R FROM SRC FILE @ID THEN
* Replace appropriate field numbers here
@RECORD<22> = R<22>
* If needed
WC_DISPLAY ACTION% = 7
WC_RESET% = 5
END
RETURN


(Volume 2 Issue 9 Page 3)
[revmedia/copyrigh.htm]

Page last modified: 08/02/03