[AccessD] Ribbon getVisible issue
Ryan W
wrwehler at gmail.com
Tue Apr 13 16:55:43 CDT 2021
https://www.access-programmers.co.uk/forums/threads/ribbon-and-user-privileges.306197/
Looks like this guy has spent some time doing what I'm trying, and yeah...
he's using local tables.
I'll have to maybe replicate my remote permissions table locally after the
linking and invalidate the ribbon and have it read out of the local table
in my getvisible function so the groups will show or hide as needed.
On Tue, Apr 13, 2021 at 3:02 PM Gary Kjos <garykjos at gmail.com> wrote:
> I'm retired now and haven't done any Access development for other
> people to use for many years. But I'm happy to see traffic on the
> AccessD list! Hope you get some suggestions!
>
> GK
>
> On Tue, Apr 13, 2021 at 2:53 PM Ryan W <wrwehler at gmail.com> wrote:
> >
> > Hey all, Sorry to bombard the group so much... I'm in active development
> > again and sometimes.. I just can't figure out the issue.
> >
> >
> > So I am attempting to call a function to determine if a ribbon group is
> > visible. This function goes out and checks the roles the user calling the
> > function has.
> >
> > The problem becomes, the ribbon initializes before my relinking
> procedures
> > do... so if I call the function to get the roles, it's calling it with
> > cached or 'old' stale credentials in some cases. I can see with exec
> > sp_who on the back end the handle stays open with my test username
> >
> > So because that SPID is held open, the query will return my elevated
> > privileges for an unprivileged user. This ONLY seems to be the case if I
> > try and use the function on the remote table for ribbon manipulation.
> >
> > Here's an image of the user BTJ logged in, but the SPID being held on the
> > SQL side is my username / spid (I was the last one to log in, before
> > logging in as BTJ).
> >
> > https://i.imgur.com/9SsE1Dz.png
> >
> > Unless there's a fix for this that makes sense I may have to make a local
> > permissions table so that the ODBC connection string doesn't impact these
> > tables before my refresh links code fires.
> >
> > Hope that makes sense?
> > --
> > AccessD mailing list
> > AccessD at databaseadvisors.com
> > https://databaseadvisors.com/mailman/listinfo/accessd
> > Website: http://www.databaseadvisors.com
>
>
>
> --
> Gary Kjos
> garykjos at gmail.com
> --
> AccessD mailing list
> AccessD at databaseadvisors.com
> https://databaseadvisors.com/mailman/listinfo/accessd
> Website: http://www.databaseadvisors.com
>
More information about the AccessD
mailing list