Etienne Charland wrote:
>
> I just tried creating a new table with a primary key of type
> 'uniqueidentifier', and adding data into it. It shows up as
> binary data.
>
This is also controlled by the "BinaryGUID" (no spaces) connection
string property. Here is an example connection string:
"Data Source=C:\\path\\to\\test.db;BinaryGUID=false;"
>
> I also tried adding "binary guid=False" to the connection string,
> but this parameter doesn't have any effect. It still treats the
> column as binary.
>
Having no spaces in the BinaryGUID connection string property name
is very important, as is matching it up the actual affinity of the
column in the target database (i.e. based on the BinaryGUID property
value used when the table was originally created).
--
Joe Mistachkin
