|
|
Posted by Erland Sommarskog on 04/22/06 14:12
Rico (me@you.com) writes:
> That would be it. I learn something new every day. ;)
>
> Thanks guys!
>
> Just out of curiosity, is there any reason why that is? I wound up
> installing a work around for the time being in the form of a stored
> procedure, but is there any resource that provides an explanation of that
> reasoning?
I don't know Access and what these "linked tables" are all about. But
I assume that you get to see the table data in some grid in Access, and
you can change data in it, and write that change back to the database.
The problem is then to locate that row in the database.
And the way to locate data in an relational database is through primary
keys, that is the data itself. So if there is no primary key, there is
no way to know which row you updated. To avoid disasters, Access is
smart enough to prevent you from even trying.
--
Erland Sommarskog, SQL Server MVP, esquel@sommarskog.se
Books Online for SQL Server 2005 at
http://www.microsoft.com/technet/prodtechnol/sql/2005/downloads/books.mspx
Books Online for SQL Server 2000 at
http://www.microsoft.com/sql/prodinfo/previousversions/books.mspx
Navigation:
[Reply to this message]
|