Larry,

>Please consider adding either...
>
>1) some kind of validation, perhaps in an Assign method
>
>or
>
>2)defining constants for the allowable values

Actually, this is the perfect place for an enumration...I debated long and hard about whether to make it a string or an enumeration, but decided on a string because it allows developers to create their own data access classes (other than the ones we already provide), whereas an enumeration would limit them to the classes already predefined in MM .NET. So...It would also be best not to put validation code in that checks for one of these three values since, again, it would prevent developers from creating their own data access classes for MM .NET.

That said, I CAN add comments to the Dev Guide where there is code demonstrating the population of the DataAccessClass property.

Regards,