Please start any new threads on our new
site at https://forums.sqlteam.com. We've got lots of great SQL Server
experts to answer whatever question you can come up with.
| Author |
Topic |
|
Lin100
Yak Posting Veteran
70 Posts |
 Posted - 2006-09-13 : 23:27:13
|
| Access 2002 and SQL Server 2000Database Type: Inspection.MDBI had a linked table. In Access, when I select a table, and then clicked on "Design",I saw a field designated as primary key, but when I go into SQL Server Enterprise Managerand I looked at the table, it had no primary key defined. There now 4 possible scenarioassociated with this. Table Name: CustomerAccess link table (Customer) SQL table (Customer) Effect on Insert, Update, Delete, etc primary key defined no primary key defined primary key defined primary key defined no primary key defined no primary key defined no primary key defined primary key defined1) How does this effect records insert, update, delete, etc... Please list the effect for each of the scenario.2) I think as a rule, no primary or index key should be defined on Access side, but defined it in SQL Server. Am I correct ?3) Under what condition would anyone wants to define the primary or index key on the Access side ? Perhaps so he could use DAO code along with ADO code ? |
|
|
timmy
Master Smack Fu Yak Hacker
1242 Posts |
Posted - 2006-09-14 : 00:00:36
|
| Access's 'primary key' for linked tables is sometimes the ones that you define when you link them in. I suggest you have a look at the Access help file with regards linking/importing. |
 |
|
|
|
|
|
|
|
Primary key in linked table on Access side