Use unique key for Sqlserver view for updates

I use an MsAccess frontend app that uses a 2 table view defined in
Sql(2005). When i link the view manually I can say (and cache in
Access) what field will be used as as primary key. This way I can
update data in the view (in both underlying tables). In fact the same
that is possible when I open the view via Sql management console.
But... normally I don't link tables manually. But then Access can't
get the information from Sqlserver what field can be used as a unique
key.
Is there a way to define such a thing in Sqlserver. Something like a
'hint' during the view definition??
Or does someone know a workaround?

On Fri, 22 Feb 2008 03:45:39 -0800 (PST), addepad
wrote:

Some views can be indexed. There are many limitations, but if you can
index yours, there is a chance MsAccess will see it. You'd have to try
that to find out.
There is no documented way to programmatically set the index fields in
MsAccess.

-Tom.


>I use an MsAccess frontend app that uses a 2 table view defined in
>Sql(2005). When i link the view manually I can say (and cache in
>Access) what field will be used as as primary key. This way I can
>update data in the view (in both underlying tables). In fact the same
>that is possible when I open the view via Sql management console.
>But... normally I don't link tables manually. But then Access can't
>get the information from Sqlserver what field can be used as a unique
>key.
>Is there a way to define such a thing in Sqlserver. Something like a
>'hint' during the view definition??
>Or does someone know a workaround?