Gary
On modern disk subsystems there is not a lot to be gained - there *is* a
trick however if you are doing very large unindexed SELECTs on very VERY
large files...i.e.
Make the file separation large - and an exact multiple of the physical disk
subsystem transfer unit size - SELECTs fly
What are you trying to send to the program? The literal '2'? If so, remove
the and from around it, those signify inline prompts in a paragraph.
Larry Hiscock
Western Computer Services
On 11/1/05, Barry Brevik [EMAIL PROTECTED] wrote:
This is UV v9.6.1.3 on Windows.
I have a paragraph
I have a program which does a PRINT @(-23) at the beginning and a PRINT
@(-24) at the end so that all the information prints on the aux
printer. Works great, but when running at one particular client site, I
get all kinds of weird characters printing on the document, at the
beginning and end
I had a site years ago where something like this was happening. The server
was in one office and remote end-users were connected over a multiplexor.
Various @ sequences were interpreted by the MUX rather than being forwarded
to the end-user. For one particular sequence, a simple @(13) to
From: john reid [EMAIL PROTECTED]
Does NFA allow ANY trigger to run across machines? I just tested with
Universe and I get a write failure with trigger code installed where
file lives, and I get an SQL error if I attempt to install the trigger
locally. Kind've the worst of both worlds.
I'll assume you wanted to prompt for a data value when the PA is executed;
just remove the if not (as others stated).
If you do, then '2' might not be the best prompt; but perhaps you meant to
use the 2nd [required] command line token? Then use C2. If you want to
prompt the user for the value
Wendy:
I have not tried this, but I would expect the trigger defined on the file
on the remote system would work fine. There is no NFA file on the 'client'
system - just an 'FX' style file pointer - so you couldn't define a trigger
to fire on an FX pointer in the 'client' environment. (using
[EMAIL PROTECTED] wrote:
From: john reid [EMAIL PROTECTED]
Does NFA allow ANY trigger to run across machines? I
just tested
with Universe and I get a write failure with trigger code
installed
where file lives, and I get an SQL error if I attempt to
install the
trigger locally. Kind've the
Sounds like a printer driver problem to me. Something like a driver
that's close but not exactly matched to the printer.
-Original Message-
From: [EMAIL PROTECTED]
[mailto:[EMAIL PROTECTED] On Behalf Of Dianne Ackerman
Sent: Tuesday, November 01, 2005 12:24 PM
To: U2 List Server
Subject:
