Simple??? form based on a view question

[Guy Kerr]

To start off I'm sorry for the cross-post but I just realized this should
probably be in this group rather than the programming group.

This is probably a stupid/simple question but one I've never taken the time
to figure out.
I have an Access ADP front-end which uses views as the source to its forms.
I have a field in my CLIENT table that I want query in my view but I don't
necessarily want to give my users the ability to update the client table.
Currently the CLIENT table is NOT part of my view.

So my form (based on the view) allows my users to insert and update records.
But I want to add a criteria to the view that says where CLIENT.DIALER =
'TRUE' so I need to join the CLIENT table to my existing view. But currently
my users don't have INSERT or UPDATE abilities on the CLIENT table. If I try
to just add the where CLIENT.DIALER = 'TRUE' (and the join to my CLIENT
table of course) without changing the INSERT/UPDATE permissions on the CLIENT
table then the entire view becomes READ ONLY. The only way I could figure
out how to fix this is to give my users INSERT/UPDATE permissions on the
CLIENT table. Is there a way to query the client table for DIALER= 'TRUE'
without having to either add the table to my view or modify the permissions
and expose the CLIENT table?

Thanks in advance

Guy

 

[Sylvain Lafontaine]

Often, it doesn't take to much to render a View or a query Read-Only under
ADP. Try setting the UniqueTable property.

A second possibility would be to replace the Join with an Exists or an IN
statement.

Finally, replacing your View with a Select query or a Stored Procedure;
along with the UniqueTable and the ResyncCommand properties could be your
ticket.

--
Sylvain Lafontaine, ing.
MVP - Windows Live Platform
Email: sylvain2009 sylvainlafontaine com (fill the blanks, no spam please)
Independent consultant and remote programming for Access and SQL-Server
(French)

 

[Belu33fr]

Addin:

UniqueTable property doesnt run if you have more 1 oriented join (directly
or/with inside a subview), if the joined table has no primarykey or if access
cannot found a primary key.

thrid possibility:View with triggers. In acces, check on the box, with view
rules and define triggers into the sql manager. You can define exactly what
you want.

Luc

 

[Guy Kerr]

Thank you both for your responses. Belu33fr thanks for clarifying the
limitations on the UniqueTable solution since am using it and it doesn't
exactly work. Your answer explains why.

Now can you clarify what you mean about option #3 - using View with
triggers? You say to check a box in Access but I'm not clear on what you
mean. Please clarify.

Thanks again to you both.

Guy