writeseq supports an ON ERROR clause and you can check STATUS() AFTER THAT
Subject: [U2] [UV] Checking file mode for type 19 item
Date: Thu, 3 Jul 2008 13:07:53 +1000
From: [EMAIL PROTECTED]
To: u2-users@listserver.u2ug.org
I need to check the write status of an item in a type 19 file.
You could also look into Ontario Systems. They work on a Cache system which
allows you to still program in Pick.
www.ontariosystems.com
-Original Message-
From: [EMAIL PROTECTED]
[mailto:[EMAIL PROTECTED] On Behalf Of Tony G
Sent: Wednesday, July 02, 2008 1:53 AM
To:
Hi Stuart,
We execute this test on the record ID in the HOLD and _HOLD_ files,
Q-pointed to the ANPHOLD file in our Pick print spooler on Universe and
Unidata.
When it is running on a .nix O.S., we use the fuser executable in our
SPOOLING phantom:
CMD = \SH -c'fuser
OK, I'm just starting out with this.
I have an existing program that has over lots of options from it that
each call a subroutine. The record id is passed to the calling
subroutine.
I need to add a new option and I want to create a AccuTerm GUI program
for it but I still need to pass in the
Couldn't you just create a wrapper that strips away the extra two and
then calls it? (Have no AccuTerm experience here, just speaking from
the pure U2 point of view)
:-)
-Original Message-
From: [EMAIL PROTECTED]
[mailto:[EMAIL PROTECTED] On Behalf Of Brenda Price
Sent: Thursday, July
If you built it as a stand alone GUI app then you can wrap the main
section of the code in a subroutine/return block and use it like any other
subroutine call. I do that for search pop-up windows currently. Just make
sure that bail-outs are handled correctly.
GlenB
-Original Message-
I have pretty extensive GED/WED experience.
GUI programs behave just the same as a regular program or as a subroutine.
You can use the @COMMAND if you wish to pass paramaters to a RUN program or
you can create the entire GED item as a called subroutine.
WHat Glen means by bail-outs are that the
