The Minister Program for Windows is fully Y2K compliant. I've checked the day of the week and leap-year calculations through 2099 and have found no problems. (After 2099 I'm not going to care!)

DOS versions of The Minister Program older than version 6.7 DO have one Y2K problem associated with printing the schedules.
The scheduler engine in the program generates a data file for each week of the year that it schedules. for example, the schedule for the first week of January 1999 will be in a file called "Jan99-1.skd". This is a data file in a format that the printing routines can read in and format for printing. The first week of January 2000 file will be called "Jan00-1.skd".

Here's the problem: I made a dumb math error for 2000 so, although the file, "Jan00-1.skd", is created and written correctly by the scheduler engine, (and the schedule information and dates in it are correct), the routine that reads it back in for printing, due to my math error, is looking for a file called "Jan 0-1.skd". (note the space between "Jan" and the single digit year where the second zero should be.) As a result, the program reports that it can't find a schedule for that week and month.

I have fixed the problem in version 6.7 and greater and will be happy to email the new version to registered users.

How to fix the version you have now: The simplest thing is to rename the schedule data files to the same time last year and then ask that the general schedule printing routines look for last year's files. For example, the schedule data files for Jan 2000 will be named "Jan00-1.skd", "Jan00-2.skd", "Jan00-3.skd" and "Jan00-4.skd". Rename them respectively to "Jan99-1.skd", "Jan99-2.skd", "Jan99-3.skd" and "Jan99-4.skd". Then tell the report routine that you want to print the schedule for Jan 99 instead of Jan 2000. This will work all right. Remember, the data in the files are correct. The problem will fix itself in 2001.