Copy to command from empty record set - bug or by design?
Tyler
tyler.style at gmail.com
Tue Jan 23 14:34:14 PST 2007
I can't tell if this is a bug in filePro or not - anyone know?
I have some code with insufficient error checking that produced an
interesting result. In some input processing, I have a lookup that
fails (the qualifier has no records in it). I then get a free record
from another qualifier, and copy the (failed!) lookup to it.
Shouldn't this error out at this point? Instead, I get a record full
of 0x00 characters (with some occasional weird non-nulls).
prc.temp
================
::end:
@keyM:::
::lookup rweb = kinotox k=1 i=A -npx:
::lookup live = kinotox at hh r=free -e:
::copy rweb to live; write live:
::msgbox ""{(live(@RN)):
::end:
command
================
/appl/fp/rclerk invhead -s1 -u -m rweb -y none -z temp
Tyler Style
More information about the Filepro-list
mailing list