Re: activating default user

HI Kirk, thanks for taking the time to weigh-in on this… I’m in need of some clarification, see below: > I include a field in the [Users] table for the database id and database > name. The significance of that value depends on the rules you set up for > yourself. I assume that these are

Re: activating default user

Robert, I include a field in the [Users] table for the database id and database name. The significance of that value depends on the rules you set up for yourself. 1) You could say the 4D structure is the authority in which case if the structure doesn't, or no longer, has that user's db id in it

Re: activating default user

Sigh, there is a hard limit of 15k admin users in the 4D User system. I am working with systems that have more than that # of users. Going to have to come up with a different approach. Thinking about having a smaller set of 4D User setup that I recycle and link them up to the users in the

Re: activating default user

Kirk, what was your method of keeping use rand 4d recs in sync? Thanks, R > On Sep 2, 2016, at 10:52 AM, Kirk Brooks wrote: > > You have to explicitly > offer some way to log in as a different 4D user or, as I eventually did, > tie my user records to a 4D user.

Re: activating default user

> On Sep 2, 2016, at 11:52 AM, Kirk Brooks wrote: > > Randy, > Not really. All logins are automatically attributed to the default user. I > used it for years with my own user login system. You have to explicitly > offer some way to log in as a different 4D user or, as I

Re: activating default user

Randy, Not really. All logins are automatically attributed to the default user. I used it for years with my own user login system. You have to explicitly offer some way to log in as a different 4D user or, as I eventually did, tie my user records to a 4D user. On Fri, Sep 2, 2016 at 7:59 AM,

activating default user

I have a need to activate the default user in the 4D password system (KB-76953 Enabling Default User) so I can get the 4D Backup progress thermometer deactivated on client machines. Is anyone aware of development 'gotchas’ or other problems that might occur which would suggest this is a bad