From: | "Sufficool, Stanley" <ssufficool(at)rov(dot)sbcounty(dot)gov> |
---|---|
To: | 'Stephen Frost' <sfrost(at)snowman(dot)net>, 'Benjamin Smith' <lists(at)benjamindsmith(dot)com> |
Cc: | "'pgsql-odbc(at)postgresql(dot)org'" <pgsql-odbc(at)postgresql(dot)org> |
Subject: | Re: MS Access and field-level permissions? |
Date: | 2010-08-17 23:19:51 |
Message-ID: | 946F457324732742B1457FAFC8CF1ECB012DD1F980FD@EXCHANGE2.sbcounty.gov |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-odbc |
Access SQL Passthrough queries should accomplish this.
>-----Original Message-----
>From: pgsql-odbc-owner(at)postgresql(dot)org
>[mailto:pgsql-odbc-owner(at)postgresql(dot)org] On Behalf Of Stephen Frost
>Sent: Tuesday, August 17, 2010 4:04 PM
>To: Benjamin Smith
>Cc: pgsql-odbc(at)postgresql(dot)org
>Subject: Re: [ODBC] MS Access and field-level permissions?
>
>
>* Benjamin Smith (lists(at)benjamindsmith(dot)com) wrote:
>> This may be a PG issue and not an ODBC issue, but Filemaker
>Pro works
>> fine with
>> the restrictive permissions, MS Access is where things break.
>
>It's actually a SQL spec requirement..
>
>> ideas?
>
>You should be able to create queries in access against just
>the fields the user(s) have access to against the linked table
>(I'd hope anyway, but I'm not an Access expert). An
>alternative would be to create views that only pull through
>the columns you want visible to your Access users.
>
> Thanks,
>
> Stephen
>
From | Date | Subject | |
---|---|---|---|
Next Message | Lord_Devi | 2010-08-18 05:45:54 | OpenOffice, Go-OO, ODBC, Offline Data Entry |
Previous Message | Stephen Frost | 2010-08-17 23:04:07 | Re: MS Access and field-level permissions? |