Dummy variables

Alan Mazuti amazu at trusteeservicesinc.com
Fri Oct 17 11:40:15 PDT 2008


I would turn the debugger on see what is happening before jumping to any
conclusions.  If anything it will at least let you know that you are running
the table you think you are running.  Just turn the debugger on for the
employee / employer combination.

Alan

-----Original Message-----
From: filepro-list-bounces+amazu=trusteeservicesinc.com at lists.celestial.com
[mailto:filepro-list-bounces+amazu=trusteeservicesinc.com at lists.celestial.co
m] On Behalf Of Steve Wiltsie
Sent: Friday, October 17, 2008 11:44 AM
To: filePro Mailing List
Subject: Re: Dummy variables

Jose,

Thanks for the quick reply.  I have inserted my responses after each of your
suggestions below.

Steve

----- Original Message ----- 
From: "Jose Lerebours" <fp at fpgroups.com>
To: "Steve Wiltsie" <swiltsie at micro-mui.com>
Cc: "filePro Mailing List" <filepro-list at lists.celestial.com>
Sent: Friday, October 17, 2008 1:29 PM
Subject: Re: Dummy variables


>I have had cases where a processing table did not work and changing the 
>dummy variable, say from aa to bb, fixed it.

I guess I could try that but all other employees' checks print just fine.

>
> 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?

They are all run at the same time - in batch.

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

In the printing processing table.

>
> 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?

I agree, but this doesn't have the extra *.  Yes, the same processing table
and form 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.

I was thinking about that - or a bad spot on the hard drive.

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


_______________________________________________
Filepro-list mailing list
Filepro-list at lists.celestial.com
http://mailman.celestial.com/mailman/listinfo/filepro-list



More information about the Filepro-list mailing list