Dummy variables

[Jose Lerebours]

Steve Wiltsie wrote:
[snip]
> The check stub has a section for deductions.  In this I print the amounts 
> for this check and the amounts for year to date for each deduction.  This is 
> done with a combination of real and dummy fields.  The YTD amounts are 
> looked up from another file and placed in the dummy fields as the checks are 
> printed.  This works fine for both companies and for every employee except 
> one.  In his case, the dummy variable for the City Tax prints the variable 
> name itself (ex: *aa).  All checks before this one and all for the other 
> company print the amount in this field instead of the variable.  This seems 
> very strange to me.
> 
> In addition, the same thing happens on this one employee's check with the 
> Social Security Number.  We print only the last 4 digits and, again, all 
> other employees' checks print the 4 digits but this same employee's check 
> always prints the variable itself.
> 
> Like I said, I've never seen this before and am trying to figure out how it 
> could happen.  It is always the same employee and always the same two 
> variables.  Has anyone seen anything like this or have an idea as to how to 
> fix it?
> 
I have had cases where a processing table did not work and changing the 
dummy variable, say from aa to bb, fixed it.

I wonder if you are running checks in batch or individually.  If 
individually, is it possible that you are running different processing 
tables given some conditions and this is causing the problem?

Are the variables defined within the printing processing table, a called 
table or automatic?

One other thing I have noticed is that if you have something like **aa 
will cause the variable to print not the value.  Additionally, are the 
checks form same for all employees?

A quick fix may be to terminate employee on file and create a new 
record.  Not sure that a corrupted record would cause such behavior.

Regards,


Jose Lerebours
954-559-7186
http://www.fpgroups.com