Behaviour of linked views in access mdb and views in project

  • Thread starter Thread starter TimS
  • Start date Start date
T

TimS

Hi

Trying my best to make a conversion from Access mdb to a
project - but continue to hit some walls....

I have an up and running access mdb with linked tables
from an SQL Server. I have set up the permissions for the
users via allowing selecting/ updating etc. on views (not
on the underlying tables). Permissions work fine - and the
user can update as I have designed.

Now with the same user accessing the same view directly
via an access project frontend - updates on the view fail
with the error message that the user does not have rights
to update the main table .....

How should I go about this correctly? The behaviour make
limited (no) sense to me at the moment.

Thanks

Tim
 
Witaj TimS,
W Twoim liœcie datowanym 4 maja 2004 (19:02:01) mo¿na przeczytaæ:

T> Hi
T> Trying my best to make a conversion from Access mdb to a
T> project - but continue to hit some walls....
T> I have an up and running access mdb with linked tables
T> from an SQL Server. I have set up the permissions for the
T> users via allowing selecting/ updating etc. on views (not
T> on the underlying tables). Permissions work fine - and the
T> user can update as I have designed.
T> Now with the same user accessing the same view directly
T> via an access project frontend - updates on the view fail
T> with the error message that the user does not have rights
T> to update the main table .....
T> How should I go about this correctly? The behaviour make
T> limited (no) sense to me at the moment.

Yes, you are right, its something wrong "written".
Because if you want to update View you have to set permission (for
select,update) to source table of that view.
But it seems that storedprocedure hasn't got that problem.
Unfortunately only views can be used in subforms connected with main
form via "connection-field"

Regards
Jacek Segit
 
Back
Top