Odd things happening...

Jeff Harrison jeffaharrison at yahoo.com
Wed Mar 2 08:44:18 PST 2005


--- Tim Fischer <tim.fischer at trinitytransport.com>
wrote:

[snip]
> 1) contrary to documentation - @sn works in
> automatic processing.  Should
> this be?  Basically if this is a bug that will soon
> be "fixed" it will break
> my code.  (I'm currently dependant upon @sn in
> automatic processing)
> 
> 2) Non-global dummy variables that are set in
> automatic processing are not
> holding their values between simple screen changes
> on the same record.  I
[snip]

1)  @sn has always worked in automatic processing. 
Where exactly does it say that it does not?  It sounds
to me like you are mis-understanding something here.

2) As I understand it non-global dummy fields will
only hold their value for the duration of the
processing table in which they are set.  If the
variable is assigned in input processing then as soon
as input processing is over then the value is lost - 
even if the field was declared in the automatic table.
 If you want the field to be available to multiple
processing tables, then make it global in the
automatic table, or use the long variable names where
you can do declare extern.

Good Luck.

Jeff Harrison
jeffaharrison at yahoo.com

Author of JHExport and JHImport.  The fastest and
easiest way to generate code for filepro exports and
imports.


__________________________________________________
Do You Yahoo!?
Tired of spam?  Yahoo! Mail has the best spam protection around 
http://mail.yahoo.com 


More information about the Filepro-list mailing list