Join The Works program to have access to the most current content, and to be able to ask questions and get answers from Revelation staff and the Revelation community

At 05 SEP 2021 01:29:17PM Richard Hunt wrote:

OI Version 9.4…

In my SOURCE application I have a file (table) called STATE. In my TEST application I have a file (table) called STATE. From my SOURCE application I "ALIAS" the file (table) STATE from the TEST application with the file (table) name of STATE_TEST. Now I have the SOURCE application file (table) TEST and the TEST application file (table) STATE_TEST. All is good so far. I can access both files (tables) with no problem.

Without going into great detail on why… When initially opening the STATE file (table), during the initial RTP57 OPEN call (with a custom MFS before the RTP57) the passed RTP57 variables are as follows…

CODE = 11

BFS = RTP57

HANDLE = The revmedia file handle for the SOURCE STATE file (table).

NAME = STATE*SOURCE

FMC = is null

RECORD = is null

STATUS = 1

And when initially opening the aliased file (table) STATE named STATE_TEST, during the initial RTP57 OPEN call (with a custom MFS before the RTP57) the passed RTP57 variables are as follows…

CODE = 11

BFS = RTP57

HANDLE = The revmedia file handle for the TEST STATE file (table).

NAME = STATE*SOURCE

FMC = is null

RECORD = STATE_TEST

STATUS = 1

So my question is… Is the RECORD variable passed by the RTP57 open call is always the alias file (table) name? And when the file (table) is not aliased then the RECORD variable is null?

Is there more info available for the RTP57 passed RECORD variable? The user help states that the RTP57 RECORD variable is "NULL" on input and the file handle on output.

View this thread on the Works forum...

  • third_party_content/community/commentary/forums_works/d5193c9d266c5b48b72800837b45949f.txt
  • Last modified: 2023/12/30 11:57
  • by 127.0.0.1