4D Server as a backend

John DeSoi (4/23/14 8:24PM)
Dave Nasralla (4/24/14 10:04AM)
John DeSoi (4/24/14 11:04AM)
Koen Van Hooreweghe (4/24/14 5:57PM)
Joshua Fletcher (4/25/14 6:39PM)


John DeSoi (4/23/14 8:24 PM)

Your link includes ODBC which in theory 4D supports directly and
should require little or no development on your part. In practice, I
have not had much luck with ODBC and third party data extraction tools
that support it. I have not tested version 13 or 14, but version 12
and prior crashed or simply did not work when trying to pull data from
4D. But it would be worth trying Winward with 4D via ODBC before
jumping into any of the more complicated options.

John DeSoi, Ph.D.

On Apr 23, 2014, at 5:44 PM, Dave Nasralla <dnasralla@...
wrote:

color><param>00000,0000,DDEE/param>IIt seems to support a wide variety
of protocols.
http://windward.net/solutions/for-your-data/

If I wanted to use 4D as a backend I get the impression I would need
to buy
a SQL Server license and then clients could connect to it via SQL.
Windward
mentions several flavors of SQL including:
- Microsoft SQL
- Oracle SQL
- MySQL
- PostgreSQL

Is it possible one of the tools for these would work with 4D?
/color>

Dave Nasralla (4/24/14 10:04 AM)

<CAHTQw=iitxMrtc2+WanqTDy9bC_eyVpv_C0Zk_PJBA5uSw6ohw@mail.gmail.com>

Thanks, Koen. That's very helpful.

On Thu, Apr 24, 2014 at 9:57 AM, Koen Van Hooreweghe
<<bvbaCompass@...
color><param>00000,0000,DDEE/param>wwrote:

I haven't done this my self, but a customers IT guy is connecting to
our
4D server for reporting purposes. I just sent him the 4D ODBC driver
installer and his credentials and he did it all by himself. He is
probably
a smart guy,
/color>

Yeah - It's always helpful to have a pretty smart guy on the other end!

dave

--
David Nasralla
Clean Air Engineering

John DeSoi (4/24/14 11:04 AM)

Dave,

I think you misunderstand 4D's SQL implementation. The only way to
connect to it from an outside application is via ODBC. Your first
paragraph below is correct -- you only need to active 4D's SQL Server
and see if the external app can work with it. But the external app
will be connecting to 4D via ODBC. I think this is what you are
looking for:

http://doc.4d.com/4D-ODBC-Driver-14/4D-ODBC-Driver.100-1365362.en.html

John DeSoi, Ph.D.

On Apr 24, 2014, at 10:41 AM, Dave Nasralla <dnasralla@...
wrote:

color><param>00000,0000,DDEE/param>TThanks for the input. It's good to
know there are options - and thats what
I'll let them know. We have a Team Developer database sandbox, and the
easiest thing for starters will be to turn on the SQL Server and see
what
happens (Lee - I don't think I'll need another SQL System.., at least I
hope not). I think you get a couple of connection licenses with Team
Developer. ?If it works well, then we can splurge on the full SQL
License
for the production machine which runs about $2000.

We will be on v14 in a couple of months and I can start playing with
the
JASON stuff.

As far as ODBC, it sounds nice, but the 4D Website is not very clear
on how
one would connect to 4D via ODBC. They mention 4D ODBC Pro expansion
for
connecting to an outside ODBC Source, but nothing about how external
databases would connect with 4D - in particular, what plugins and
licensing
your need.
/color>

Koen Van Hooreweghe (4/24/14 5:57 PM)

Dave,

This is not very difficult.
Just install the ODBC driver on the client side, setup the ODBC source ?

and have the external app use that source.
The 4D ODBC driver is part of the full 4D download. The manual in pdf ?
format is included.

You will have to start the SQL server on your 4D server, because ODBC ?
is connecting to the SQL server.

Keep in mind active SQL connections (in this case the ODBC flavor) are ?

eating up a client license. Which you can 'prevent' by buying and ?
installing the unlimited SQL server license.
So, you can test with your current 4D server license.

I haven't done this my self, but a customers IT guy is connecting to ?
our 4D server for reporting purposes. I just sent him the 4D ODBC ?
driver installer and his credentials and he did it all by himself. He ?
is probably a smart guy, but I'm sure the installation setup is pretty ?

straightforward.

HTH
Koen

Op 24-apr-14, om 17:41 heeft Dave Nasralla het volgende geschreven:

color><param>00000,0000,DDEE/param>AAs far as ODBC, it sounds nice,
but the 4D Website is not very clear ?
on how
one would connect to 4D via ODBC. They mention 4D ODBC Pro expansion ?
for
connecting to an outside ODBC Source, but nothing about how external
databases would connect with 4D - in particular, what plugins and ?
licensing
your need.
/color>

--------------------
Compass bvba
Koen Van Hooreweghe
Kloosterstraat 65
9910 Knesselare
Belgium
tel +32 495 511.653

Joshua Fletcher (4/25/14 6:39 PM)

If external app = non-4D app then everything below is true. =A0Others
have already mentioned how this can be done 4D-to-4D via "direct
connection":

http://kb.4d.com/assetid=76310

Regarding licensing, details are here:

http://www.4d.com/products/4dv14/deployment.html

In particular the "Deployment feature" is "SQL Server".

-Josh

--
Josh Fletcher
Technical Account Manager
4D, Inc

color><param>00000,0000,DDEE/param>
/color>

-----Original Message-----
color><param>00000,0000,DDEE/param>II think you misunderstand 4D's SQL
implementation. The only way to connect
to it from an outside application is via ODBC. Your first paragraph
below
is correct -- you only need to active 4D's SQL Server and see if the
external app can work with it. But the external app will be connecting
to
4D via ODBC. I think this is what you are looking for:

http://doc.4d.com/4D-ODBC-Driver-14/4D-ODBC-Driver.100-1365362.en.html
/color>

Reply to this message

Summary created 4/25/14 at 6:57PM by Intellex Corporation

Comments welcome at: feedback@intellexcorp.com