Access 97/Windows 2000
Problem: Primary key thinks upper and lower case are the same.
I cannot create a key or non-duplicate index on a column whose values may be differentiated only by case. For example, Access treats "LC1030280T" and "LC1030280t" as the same and therefore I cannot build a key or index on this column.
Q1 Do you know how I can create a table in Access so that columns are case-sensitive?
or if not..
Q2 Do you know of any environment/global variables that may influence the Access default behaviour for a database instance, or hopefully at least at the table-level, if not column-level?
Q3 Any ideas I could use as a 'fudge'?
-I've thought about creating another table in Access to hold the 'duplicates' - but then need messy UNIONs in all joins.
Why I need this: I'm synchronising an Ingres 6.4 DB with Access using a background application, (C++Builder/Delphi). When tables change in Ingres a rule(trigger) is fired and the Delphi app. updates the relevant record(s) in Access using the key(s) to reference the record(s).
I suspect there is a bug in our Ingres apps. because we normally apply a standard of uppercase for all key columns and build this into the form's data validation code.
Problem: Primary key thinks upper and lower case are the same.
I cannot create a key or non-duplicate index on a column whose values may be differentiated only by case. For example, Access treats "LC1030280T" and "LC1030280t" as the same and therefore I cannot build a key or index on this column.
Q1 Do you know how I can create a table in Access so that columns are case-sensitive?
or if not..
Q2 Do you know of any environment/global variables that may influence the Access default behaviour for a database instance, or hopefully at least at the table-level, if not column-level?
Q3 Any ideas I could use as a 'fudge'?
-I've thought about creating another table in Access to hold the 'duplicates' - but then need messy UNIONs in all joins.
Why I need this: I'm synchronising an Ingres 6.4 DB with Access using a background application, (C++Builder/Delphi). When tables change in Ingres a rule(trigger) is fired and the Delphi app. updates the relevant record(s) in Access using the key(s) to reference the record(s).
I suspect there is a bug in our Ingres apps. because we normally apply a standard of uppercase for all key columns and build this into the form's data validation code.
