OK, Bill, I've taken your advice. I removed the schedule from the job and then created a new one, with a different name (I don't know if the old schedule is still out there or not). As it turns out that SQL job was the only one that used that schedule, so I don't harm anything else. Then I double checked it in Activity Monitor, and it now shows it as going to run on April 1st, which is what I want it to do.

Just out of curiosity, suppose I or someone else, were to run that SQL job manually before then? Will it still run on 4/1/2014 @ 12:05 AM? Or would it be rescheduled?