Adam,
This is not unique to Access 2013. I've had it happen to me when linking to a table that doesn't have a primary key defined. I don't know why anyone would do that but sometimes they do. If you can, have a primary key designated on the table and if you can't, then choose a combination of fields that make a record unique.
Doyce
---In MS_Access_Professionals@yahoogroups.com, <duanehookom@...> wrote :
Adam,
This hasn't happened for me. If you don't specify a key field and then go to the table design in Access do you see a primary key? How about a unique index?
Does your SQL table have a Primay Key defined or only a unique index?
Duane Hookom, MVP
MS Access
This hasn't happened for me. If you don't specify a key field and then go to the table design in Access do you see a primary key? How about a unique index?
Does your SQL table have a Primay Key defined or only a unique index?
Duane Hookom, MVP
MS Access
To: MS_Access_Professionals@yahoogroups.com
From: MS_Access_Professionals@yahoogroups.com
Date: Thu, 11 Feb 2016 06:29:42 -0800
Subject: [MS_AccessPros] Linking to SQL
Why does Access (2013) make me select key fields, when linking to SQL tables, when they are already defined in SQL? Does it matter?
Adam
From: MS_Access_Professionals@yahoogroups.com
Date: Thu, 11 Feb 2016 06:29:42 -0800
Subject: [MS_AccessPros] Linking to SQL
Why does Access (2013) make me select key fields, when linking to SQL tables, when they are already defined in SQL? Does it matter?
Adam
__._,_.___
Posted by: winberry.doyce@roadsysinc.com
| Reply via web post | • | Reply to sender | • | Reply to group | • | Start a New Topic | • | Messages in this topic (3) |
.
__,_._,___
Tidak ada komentar:
Posting Komentar