Entity history log (OpenInsight Specific)
At 04 OCT 2001 02:35:49PM Wilhelm Schmitt wrote:
Regarding the entity history log:
1) Is it possible to flag any file to be included in the updates for SYSREPOSLOG?
2) Is there any problem on updating SYSREPOSLOG from AREV?
Although I do not use check-in/out, the history log becomes handy during development.
Thanks in advance.
Wilhelm
At 05 OCT 2001 10:20AM [url=http://www.sprezzatura.com" onMouseOver=window.status=Click here to visit our web site?';return(true)]The Sprezzatura Group[/url] wrote:
As far as I know, there's no real way to do this. The SYSREPOSLOG is only updated through the repository functions. While there is a way to extend the repository, in order for the system to update the log seemlessly, you'd have to do all of your access through REPOSITORY methods.
As for accessing the SYSREPOSLOG file from ARev, there's no reason why you can't. An LH file is an LH file is an LH file.
Another option is placing an MFS on the file and letting that update the log.
World Leaders in all things RevSoft
At 05 OCT 2001 10:27AM Wilhelm Schmitt wrote:
Thanks Sprezz,
I just wanted to make sure that SYSREPOSLOG is not one of those files with special functions, which may go crazy when updating from outside.
I think the MFS will be the easiest way.
Wilhelm
At 05 OCT 2001 10:34AM [url=http://www.sprezzatura.com" onMouseOver=window.status=Click here to visit our web site?';return(true)]The Sprezzatura Group[/url] wrote:
As far as I know, the only file that should not be access from ARev 3.1x is SYSREPOS since that file is encrypted.
You could access this from ARev for view only or to delete a corrupted record. However, you'd have to rebuild the repository indexes from OI afterwards. I'm not exactly sure what sorts of flags the repository mirror would kick out though.
World Leaders in all things RevSoft