Here is your Pig in a Poke order.
John Esak
john at valar.com
Fri May 27 10:23:04 PDT 2005
> -----Original Message-----
> From: Dick Burke [mailto:rjburke at hal-pc.org]
> Sent: Friday, May 27, 2005 11:37 AM
> To: john at valar.com
> Subject: RE: Here is your Pig in a Poke order.
>
>
> John, I set pfformsize=80000 and it works now.
>
> Why does this need to be set, as I see no form command in any of
> the prc tables ?
Dick,
It is odd, but forms and call tables use the same area in memory. This has
been cause for some trouble in the past, but I believe Ken has reworked
things a lot in the later versions of FP so it is no problem anymore... if
you use the PFFORMTOKSIZE setting. The name was already there for FORMS, so
rather than add a whole 'nother variable just to cover the CALL table stuff
when it got added, I believe he just rolled it all into this one variable.
The way I'm doing the "pig" demo is as a CALL table. You can easily put the
whole prc table into an INPUT table or any clerk table, though. However if
you just pass this table a filename as I have shown, it is very efficient
and portable *as* a CALL that you can use from all your different filePro
files.
If you are on 5.0+ then you can use all declared variables on this call
table, making it completely compatible with every other prc you have.
Otherwise, you have to leave it as it is defaulted in the 4.8 condition
where it uses the 2 character variable l (el). Who knows? Maybe someone has
written a 4.8 prc table that has a global variable l already and by calling
this table, it could screw up how that is working. That is why I like 5.+,
you can write call tables to be completely DECLARED so they never conflict
with any 2 character variable you may be using on other tables.
John
P.S. There is no harm in keeping all the TOK variables, PFTOKSIZE,
PFAUTOKSIZE and PFFORMTOKSIZE at reasonably high values like 100000. The
memory hit is not bad at at all. By the way, I just guessed at 8000, it
might work at much lower than that... it obviously just doesn't work at the
default filePro value.
I hope you won't mind that I'm going to cc this to the list just in case any
others who have gotten the program have the same trouble you did. Thanks.
More information about the Filepro-list
mailing list