If I manually set the value to True in the tables then create a new
database from that recordset, the correct Unicode Compression value is
created correctly.
Interestingly...
If I change the memo field to a text field (with unicomp set to true),
save the table/field changes, then change the text field back to a
memo field and save the changes, my code reads the correct value for
Unicode of the Memo field.
So it would appear that if a field is created as a memo field and
unicomp property is set to true, it doesnt read correctly with ADOX.
If a field is set as a text field with unicomp set to true then
changed to a memo field, it will read correctly (true or false).