Sign Up to our social questions and Answers Engine to ask questions, answer people’s questions, and connect with other people.
Login to our social questions & Answers Engine to ask questions answer people’s questions & connect with other people.
Lost your password? Please enter your email address. You will receive a link and will create a new password via email.
Please briefly explain why you feel this question should be reported.
Please briefly explain why you feel this answer should be reported.
Please briefly explain why you feel this user should be reported.
Defining some Tables in SQL-Server which will be accessed via ODBC from MS-Access.
I’m not sure about it, put i read somewhere that a primary key must bee named with ‘aaaaaPK_ColumnName’.
The 5 ‘a’ should manage that the PK is listed first in the dialog for all key’s in MS-Access.
What do you think about that?
I found, that a the only rule is to have a good primary key defined. The Name of the key isn’t that importand (shouldn’t be too long).
Do not define more than 31 Keys if you want that access don’t throw an error.
Thats all if you do not have the sql-table under replication. in this case choose a primary key with a characterbased datatpye. numeric datatypes in primary key have conficts with the sql2008 merge replication-insert-triggers.
sql2000 does not have this constraint, because the merge replication – insert-trigger do not populate a table with a identity-column.
beside good primary key(s) a column with a datatype timestamp in each table is also recommended.