On 08/11/12 00:47, dennis bartlett wrote:
> Once again (I'm a fan of these) the answer is to create a file of composite
> keys (FldA * FldB etc) and index that...
>
> The bummer is that the xref file will always be out unless one adds a
> 'trigger' to each 'to be indexed' file
Are you SURE?
> It
Hi Kevin,
Two times in my Unidata career I've had a problem like this where
something doesn't work in a subroutine. My work around, both times, was
to add a simple line of code at the beginning of the program. Usually
just assigning a value to a new, unused, variable like JUNK="JUNK" is
all it w
FWIW not just @VM. I have standard include code that does a CONVERT
CHAR(222) TO @FM after doing MCU conversions on UniData. Since it just gets
poked in various places I haven't checked if it is still a problem.
BASICTYPE P, but no other UDT.OPTIONs strangely set ..
Brian
-Original Message--
Kevin:
Many releases ago on Unidata we noticed that this particular code was not
working. The code would work when we had it in another program. The
program would fail even when we added CRT statements around the code. So,
we moved the offending code to another area of the program and the probl