Re: 4D 11 SQL Licensing Issues

John,

Re:
> Right, it absolutely is referring to access to non-4D systems. In the past
> 4D was useful in the role as a client to a foreign database, and it was
> marketed that way. Now apparently that option is closed off unless you pay
> huge license fees.

I was thinking about the situation with connecting to an SQL database and
realised that technically it is not 4D that is making the connection it is
actually the plug-in.  I am then binding the resulting data to arrays and
variables held locally.  So this should not be an issue...

I believe that they must be simply clarifying that this is not a server
product and that to use it for "SQL Pass-through or ODBC Login" for instance
you would need SQL Desktop.

Any other assertion becomes odd the more you think about it.  Jan-Willem
stated he carried out imports and exports to other systems.  Taking the hard
line I would only be allowed to import/export via file, ftp or any other
communication method twice a day.  I would not be allowed to integrate email
or any communication method nor access documents on a remote volume more
than twice a day.

I think we have to be realistic in this.

If this is not the case then it would be better for me to buy 4D Developer
Standard and SQL Desktop when needed.  Given the low number of clients I
deploy this solution for it would probably work out cheaper and I would move
the costs to deployment not development.