I have pored over the header files and searched MSDN and don't see an
obvious way to bind to GUID fields in Access or SQL Server tables. I
suppose you could bind to a CByteArray, but this seems a ludicrous amount
of overhead to support 16 byte values.
Does anyone have any experience with this? We are trying to port an Access
application to ODBC (specifically SQL Server), and the GUID type seemed a
logical replacement for our use of autonumber fields. I know that we could
also use IDENTITY columns, but we also use our counters for referential
integrity and GUID's would seem to have the natural advantage of being
(optionally) generated prior to actually writing the records.
Randy Baker (remove Z from address in email replies)