Shawn,

>Okay? It makes sense i think, not sure why the design would be that way, but okay.
>If i know what the field is going to be, i guess why would i add the overhead of having a property as object versus a defined string or numeric type.

Bonnie's right...at the Framework level I don't want to dictate the data type of primary keys. Specifying the values as System.Object allow the Framework code to work regardless of the data type.

Regards,