I think the purpose of the trigger is to capture all non-application
changes.
You can't by-pass the trigger easily, unless of course you disable it
entirely.
It has the advantage of being largely transparent (if written correctly,
of course)...regards of where the file is accessed from. It has
There is still a hole to the wrapper approach.
Assuming you are trying to catch folks that use the ED (or AE) command, we
have to assume that these folks have access to TCL. If you can get to TCL, and
you are wanting to hide your tracks, you could still copy your record to a dir
file, then
Yep - pretty much.
1 - Globally cattledog the subprograms - otherwise it could crash your
update
2- If the subs change - recattledog them and they will reflect the
change immediately.
I'll see if I can put an eg up on the wiki tomorrow.
Stuart Boydell
-Original Message-
Are you saying
Running Universe 10.0.17 on Windows Server 2003 32bit:
Can I create a distributed file for a data file that is part of shared
dictionary (ie a multi-level data file)?
I can't seem to get the syntax right.
Here is the scenario. We have a large stock file with current
transactions called
Don't forget Remote Verbs (aka Security Subroutines). The combination of
triggers and remote verbs is pretty robust, but not rock solid if someone
has access to the REAL O/S outside a database shell (for DIR files anyway).
Regards
JayJay
-Original Message-
From: [EMAIL PROTECTED]
This makes very good sense to use EQU TO and EQU LIT.
The technique is considered pretty standard in other languages which
have specific constant macro constructs. There are also very good
semantic and source quality imperatives to use this type of technique.
Cheers,
Stuart Boydell
Troy,
You _can_ use 64-bit files on 32-bit Windows 2003 Server, NTFS is quite
happy with files over 2GB.
I would describe multi-level files as an 'old' way of getting some of
the same functionality as you get with UV Distributed files. You could
have STOCK,HIST1 and STOCK,HIST2 ... if you
I'd do something like this paragraph (not tested...) but it should
create the parts and update them to all point to the same dictionary.
0001 PA
0002 CREATE.FILE DICT TEST.SHARED.DICT 3
0003 CREATE.FILE DATA TEST.P01 DYNAMIC
0004 CREATE.FILE DATA TEST.P02 DYNAMIC
0005
0006 DISPLAY UPDATING