× The internal search function is temporarily non-functional. The current search engine is no longer viable and we are researching alternatives.
As a stop gap measure, we are using Google's custom search engine service.
If you know of an easy to use, open source, search engine ... please contact support@midrange.com.



Hi Jim,

On 2/10/2011 1:59 PM, Jim Wiant wrote:
I did some digging and I can't find a way to override or control the
system date other than changing the date, which again is not my first
choice because it will affect all testing not just the one I want and
the impact on the journals scare me anyway.

Back during the time when we were testing Y2K stuff, we bought a product called "AnyDate" that let us override the system date. That product appears to still be for sale today (though, I haven't used it since 1999)
http://www.sequel-software.com/products/anydate

I don't know if it changed, but back in 1999, it essentially consisted of two commands:

OVRSYSDATE = override system date
DLTDATEOVR = delete date override.

So you'd run OVRSYSDATE to override the system date. While that command is in effect, %DATE(), %TIMESTAMP(), the TIME opcode, RTVSYSVAL QDATE, etc, would return the date you provided on the OVRSYSDATE. When you ran DLTDATEOVR, it'd revert to getting the date from the clock as normal.

So that might help you?


As an Amazon Associate we earn from qualifying purchases.

This thread ...

Follow-Ups:
Replies:

Follow On AppleNews
Return to Archive home page | Return to MIDRANGE.COM home page

This mailing list archive is Copyright 1997-2024 by midrange.com and David Gibbs as a compilation work. Use of the archive is restricted to research of a business or technical nature. Any other uses are prohibited. Full details are available on our policy page. If you have questions about this, please contact [javascript protected email address].

Operating expenses for this site are earned using the Amazon Associate program and Google Adsense.