future date testing

[Fairlight]

When asked his whereabouts on Thu, Jun 03, 2010 at 02:51:31PM -0400,
Boaz Bezborodko took the fifth, drank it, and then slurred:
> Why not write the FPro routine to look at a declared variable instead of 
> @td and then load that variable to @td+"30"?
> 
> Then, when you go into production all you have to do is remove the 
> '+"30"' to have it read the present system date.  Al the rest of the 
> routine should remain the same.

Interesting concept for processing you control--wherever there's a time
formula, use what you're suggesting.  Creative.

The problem I see is in what you can't control-- at cd, @ud, et al.  Those are
set by internal time calls in *clerk/*report, and you can't manipulate what
they do at the record level.  So if even some of the attendant testing
relies on anything uncontrollable by processing, you're better off just
using a virtual environment.

mark->
-- 
Audio panton, cogito singularis,