Hard to give a specific answer without knowing the specifics of your accounting system, but most of the systems I've seen, and indeed the home-brewed system we use, don't rely on the OS date, rather most dates are specified in functions as a parameter. Does your system "automagically" close the books based on the system date? We rarely "close the period" exactly on the last day of the month. Sorry, probably not much help.

examples:
CREATE PROC cm_sp_Ar_Aging
@pCoNo VarChar(10),
@pAgingDate DateTime
AS
...
/* code for ar aging report */

cm_sp_ArAging 'sc', '7/31/2003'

-or-

CREATE PROC cm_sp_Ar_ClosePeriod
@pCoNo VarChar(10),
@pPeriod Int
AS
...
/* code for closing the period */

cm_sp_ClosePeriodAR 'sc', 200307

-Greg



-----Original Message-----
From: Gary Fahrlander [mailto:gary.[Email Address Removed] Wednesday, August 27, 2003 10:24 AM
To: LazyDBA.com Discussion
Subject: Tools question






We've got an environment that we need to do date specific testing for
accounting. That is, start with today's date and then change the date to
simulate month-end and close/balance the books. Then move the date up
again to simulate the following month-end.

Does anyone know of any product or tool that would allow us to make the
application think it's in the future without having to change the current
date on the server?

We encountered problems with the domain controller, licenses, passwords,
etc. when we changed the server date.

Thanks,
Gary


---------------------------------------------------------------------
TO REPLY TO EVERBODY , PLEASE CLICK REPLY-ALL, NOT JUST REPLY
To unsubscribe, e-mail: mssqldba-[Email Address Removed] additional commands, e-mail: mssqldba-[Email Address Removed]MS Sql Server LazyDBA home page