C
Christine
I am working on a method for updating table schema on customer
databases out in the field. I notice that when I add a field using DAO
code, it has a CollatingOrder of 1024. But when I add a field using
the interactive Design View technique, it has a CollatingOrder of
1033. The CollatingOrder does not seem to be editable. I am using
Access 2000.
1. What does CollatingOrder 1024 mean? 1033 is dbSortGeneral. 1033 =
1024 + 9, so perhaps there are those 2 extra bits set to go from 1024
to 1033 that have some meaning.
2. Is there anything I can do to have my code added fields have the
1033 CollatingOrder? In my experimenting, I do not do anything that
would change the DB collatingorder between trying out a code field add
and the Design View field add.
3. Does it really matter at all? In other words, is 1024 'as good' as
1033. My customers are all U.S. based - no foreign languages involved.
Many thanks to all of you out there who help out most generously with
your experience and words of wisdom.
Christine
databases out in the field. I notice that when I add a field using DAO
code, it has a CollatingOrder of 1024. But when I add a field using
the interactive Design View technique, it has a CollatingOrder of
1033. The CollatingOrder does not seem to be editable. I am using
Access 2000.
1. What does CollatingOrder 1024 mean? 1033 is dbSortGeneral. 1033 =
1024 + 9, so perhaps there are those 2 extra bits set to go from 1024
to 1033 that have some meaning.
2. Is there anything I can do to have my code added fields have the
1033 CollatingOrder? In my experimenting, I do not do anything that
would change the DB collatingorder between trying out a code field add
and the Design View field add.
3. Does it really matter at all? In other words, is 1024 'as good' as
1033. My customers are all U.S. based - no foreign languages involved.
Many thanks to all of you out there who help out most generously with
your experience and words of wisdom.
Christine