Re: 4D Write Pro license question

2019-01-14 Thread Kirk Brooks via 4D_Tech
On Mon, Jan 14, 2019 at 10:55 AM Guy Algot via 4D_Tech <4d_tech@lists.4d.com> wrote: > I was using groups and BLOB TO USERS and although groups would be > restored, any changes to groups would not. So perhaps a bug in USERS TO > BLOB? > That's really not a good thing. -- Kirk Brooks San

Re: 4D Write Pro license question

2019-01-14 Thread Guy Algot via 4D_Tech
Koen, This problem also exists in v15 (and v13). I was using groups and BLOB TO USERS and although groups would be restored, any changes to groups would not. So perhaps a bug in USERS TO BLOB? > On Jan 14, 2019, at 4:01 AM, Koen Van Hooreweghe via 4D_Tech > <4d_tech@lists.4d.com> wrote: > >

Re: 4D Write Pro license question

2019-01-14 Thread Koen Van Hooreweghe via 4D_Tech
Hi Chuck, IMHO this is not correct. I recently struggled a lot with 4D View (Pro) licenses. A customer has 40+ users on 4D Server (v16), but only a few of them need 4D View. So they bought a 5 user license. These are my findings : - if there are no user groups, the licenses are assigned upon

Re: 4D Write Pro license question

2019-01-13 Thread cjmiller--- via 4D_Tech
You. An create a group called 4d write group. It iS the first people who use 4d write code not just logging in Regards Chuck Sent from my iPhone > On Jan 13, 2019, at 5:30 PM, Pat Bensky via 4D_Tech <4d_tech@lists.4d.com> > wrote: > > Kirk, > As I understand it - and no doubt somebody will

Re: 4D Write Pro license question

2019-01-13 Thread Kirk Brooks via 4D_Tech
Thanks Pat. That makes sense and explains the approach of assigning plug in access with user groups. And it's a push to sell more licenses. On Sun, Jan 13, 2019 at 2:31 PM Pat Bensky via 4D_Tech <4d_tech@lists.4d.com> wrote: > Kirk, > As I understand it - and no doubt somebody will correct me if

Re: 4D Write Pro license question

2019-01-13 Thread Two Way Communications bvba POP via 4D_Tech
I guess you’re wright, Pat. As Kirk mentions, the question is when the license is released. I’m afraid this is only when a user logs out, but I haven’t tested it. I try not to use too much stored procedures on 4D server, though. I did this when an application of mine was deployed the first time

Re: 4D Write Pro license question

2019-01-13 Thread Pat Bensky via 4D_Tech
Kirk, As I understand it - and no doubt somebody will correct me if I'm wrong :) - a plugin licence is assigned to a user when they log in, and they keep that licence until they log out. They are assigned in the order people log in. So, say you have a 10-user system but you have only 4 WP

Re: 4D Write Pro license question

2019-01-13 Thread Kirk Brooks via 4D_Tech
Thank Pat, That's what I thought. Since you are very familiar with using Write Pro - I assume licenses 'consumed' when a user invokes a method or opens a a form that requires one. Is that license 'released' as soon as it's no longer being used? Obviously I'm trying to understand how many

Re: 4D Write Pro license question

2019-01-13 Thread Pat Bensky via 4D_Tech
Hmmm Rudy, I would suggest that if the server (or any stored process) needed to use a WP licence, even for a second, then you WOULD need to reserver a licence for it. Otherwise you would easily run into a situation where all available licences have been used by connected users, and then it

Re: 4D Write Pro license question

2019-01-12 Thread Two Way Communications bvba POP via 4D_Tech
Hi Kirk, My guess is that, as long as the ‘Designer’ user belongs to a group that is linked to 4D Write plugin, the 4D Write PRO code will work in the stored method. It will temporarily use up 1 of the licenses available, but only for a short time. As such, you do not really need to

4D Write Pro license question

2019-01-12 Thread Kirk Brooks via 4D_Tech
Does 4D Server require a 4D Write Pro license for non-UI methods? Let's say I have a database with 10 4D Write Pro licenses. I may have more than 10 users and understand how to check and manage licenses available for users. My question is if I have to 'reserve' a license for the server to be