You know, this reminds me of when I used to manage restaurants. I'd tell my
managers that a place runs better when it's easy to do the right thing and
hard to do the wrong thing. So you really want to avoid making it easier to
do the wrong things. Because the easier something is to do the more like
Hi
,
Just some more clarification on licensing.
Not many people read the fine print of the license.
A
4D Application Single User (or what many people call
engined
or
sponsored version
)
can’t
connect more than twice per day to write to a data source. It can
connect as many times as y
> If you use SQL there is no additional licensing needed.
This is incorrect; or at least it is misleading...
If using SQL, and you do not have an "Unlimited SQL License", then each SQL
connection will consume a Client License on the 4D Server.
Therefore, if there is no more 4D Client licenses av
Hi,
Chipping in on the licensing question.
What is the standalone?
If it’s a sponsored 4D engine app then you are limited to two connections
per day.
If it’s SQL desktop app then you can connect whenever you want. I assume
the same for the developer editions too.
The oem desktop product could
Chuck,
Good point. I assumed he already has a web license but if that's not the
case you are correct.
On Tue, May 8, 2018 at 9:25 AM Charles Miller via 4D_Tech <
4d_tech@lists.4d.com> wrote:
> If you use SQL there is no additional licensing needed. The other SOAP or
> HTTPS means another license
If you use SQL there is no additional licensing needed. The other SOAP or
HTTPS means another license either for soap server or web server on the 4d
server
Regards
Chuck
On Tue, May 8, 2018 at 11:53 AM, Kirk Brooks via 4D_Tech <
4d_tech@lists.4d.com> wrote:
> David,
> What version of 4D are you
> On May 8, 2018, at 4:48 PM, David Loeppky via 4D_Tech <4d_tech@lists.4d.com>
> wrote:
>
> I have a standalone 4D application that needs to occasionally connect to
> our 4D Server to exchange some data. Realizing there are a few different
> architecture approaches to take, I'd appreciate some
David,
What version of 4D are you using? If it's v15+, with respect to Chuck's
suggestion, I'd use HTTPS for the data transfers and JSON/c-objects. It's
pretty easy to write an API on the server side to manage such a request and
shuffle the data between the two endpoints. JSON is a lot easier to wo
It all depends. How much data is exchanged? How automated do you need it to
be? How often will you be doing this? Is data movement bi-directional?
The most straightforward IMO is SQL, but you could also use SOAP, text(XML
files), HTTPS
Regards
Chuck
On Tue, May 8, 2018 at 10:48 AM, David Loeppk
I have a standalone 4D application that needs to occasionally connect to
our 4D Server to exchange some data. Realizing there are a few different
architecture approaches to take, I'd appreciate some advice as to the
easiest way to approach this. Thanks.
--
Regards,
David Loeppky
Co-Owner
T:
10 matches
Mail list logo