>I realize that if they enter a 4 digit year for that date we will be fine. I just don't see that being a feasible solution (meaning that I am not sure if this will be considered an acceptable solution with our Y2K Project Office Team). Thanks for your help though.

If entering a four digit year for 2/29/2000 is not acceptable, then your best bet is probably to go with Chistof Lange's solution or Y2KFox, both of which -- as I understand it -- allow the user to enter 2/29/00.

For my part, I'm just happy as heck that I chose Fox as my primary development tool several years ago, since our Y2K issues are almost nil in comparison to others. I used to be a COBOL programmer (at a bank, by the way) and I'm _really_ glad I don't have to retrofit all that old code and file structures!