Re: I4GL licenses

Mrinal Kant said: > Hi Obnoxio (and anybody who can help), > thanks for the input. But my confusion prevails owing to the following > reasoning: > > Once a developer has written a 4GL program and compiled and linked it into > an executable, the executable is like any other executable that could have > been written using C etc. and without using 4GL. I mean there is no > distinction between executable coming from 4GL compile and link or > otherwise. > > If the above is true, all I do while running the executable is access the > library functions and set up a session with the Informix dynamic server. > Consequently, running the executable should have nothing to do with I4GL > licenses (development or runtime). > > Had it been RDS, runtime licenses were understandable because the > execution > would require the use of p-code runner which is a part of the RDS. But in > the case of 4GL compiler, runtime licenses should have nothing to do with > the running of the programs which the developers have written. Why, then > as > you say, should I need 20 runtime licenses for 20 users to run what the > developers have written, compiled, linked and given to the users to run? > > As an analogy, if I developed an application with some other development > environment (Microsoft Visual C++, say) using statically linked libraries > and then deployed the executable to other machines for the users of the > application to run, would I need to have some kind of runtime licenses for > legally running the developed applications? Your analogy is wrong. Even though the applications are statically linked, compiled programs, the licensing agreement for 4GL is different from the licensing agreement with Microsoft Visual C++. -- Bye now, Obnoxio "C'est pas parce qu'on n'a rien ' dire qu'il faut fermer sa gueule" - Coluche did i mention i like nulls? heck, i even go so far as to say that all columns in a table except the primary key could/should be nullable. this has certain advantages, for example, if you need to insert a child record and you don't have a parent row for it, just do an insert into the parent table with the primary key value (everything else null), and voila, relational integrity is preserved. but this is, admittedly, a bit controversial among modellers. --r937, dbforums.com