DATES.VCX by David B. Diehl is being release into the public domain with no
warranties, written or implied.

There is also a sample form to test the functionality of this concept.

DATES.VCX contains only one class, txtDateBox. The idea here was to develop
a method to overcome the problems associated with the turn of the century. I 
for one am not happy with the solution of using the SET CENTURY command. This 
would require the user to enter a four digit year and for me is unacceptable.
The retraining of years of practice for the user in entering an eight digit year
over the current six digits leaves us all open to an extreme amount of potential
data entry error.

The new class is a text box. There is one added Property called Epoch. This property
will contain the "Epoch" date for the field, etc. being entered. Since all dates in
VFP default to the 20th century, this epoch date must be during this century. Any 
date that is entered that is before this date will automatically be converted to
the next century. This property can be changed at run time also, allowing you
to build as much flexibility into your system as required.

EXAMPLE:	a txtDateBox object with an Epoch property value of {01/01/50}

		User enters a date of 12/07/41 returns a value of 12/07/2041 while
		     an entry of 12/07/50 returns a value of 12/07/1950.

I hope this helps you in overcoming some of the problems associated with the 
turn of the century. I would assume that upcoming releases of VFP will have some
method of handling this problem built in.

I would be interested in hearing any comments, etc. I can be reached on Compuserve
at 76325.3001.


