Chuck

Re: SQL LOGIN(“IP:ipaddress:port:ssl”;"user”;"Userpassword";*)

That did it. Thanks!

Steve


> On 9 May 2018, at 21:50, Charles Miller via 4D_Tech <[email protected]> 
> wrote:
> 
> Try adding the port to ip address and I always connect using IP not DB so
> connection would look like 192.168.5.12:19812
> 
> Regards
> 
> Chuck
> 
> 
> 
> On Wed, May 9, 2018 at 4:47 PM, Stephen Shaw via 4D_Tech <
> [email protected]> wrote:
> 
>> 
>> 
>> Chuck
>> 
>> Thanks for answering
>> 
>> SQL is running and shows the active connection when the code is run from
>> the client
>> I have just copied the code to a single user database and I am on the same
>> network and subnet
>> 
>> Steve
>> 
>> 
>>> On 9 May 2018, at 21:24, Chuck Miller via 4D_Tech <[email protected]>
>> wrote:
>>> 
>>> Are you sure that
>>> 1. SQL server is running
>>> 2. you are trying to connect to same place
>>> 
>>> Regards
>>> 
>>> Chuck
>>> ------------------------------------------------------------
>> ------------------------------------
>>> Chuck Miller Voice: (617) 739-0306
>>> Informed Solutions, Inc. Fax: (617) 232-1064
>>> mailto:cjmiller<AT SIGN>informed-solutions.com
>>> Brookline, MA 02446 USA Registered 4D Developer
>>>    Providers of 4D and Sybase connectivity
>>>       http://www.informed-solutions.com
>>> ------------------------------------------------------------
>> ------------------------------------
>>> This message and any attached documents contain information which may be
>> confidential, subject to privilege or exempt from disclosure under
>> applicable law.  These materials are intended only for the use of the
>> intended recipient. If you are not the intended recipient of this
>> transmission, you are hereby notified that any distribution, disclosure,
>> printing, copying, storage, modification or the taking of any action in
>> reliance upon this transmission is strictly prohibited.  Delivery of this
>> message to any person other than the intended recipient shall not
>> compromise or waive such confidentiality, privilege or exemption from
>> disclosure as to this communication.
>>> 
>>>> On May 9, 2018, at 3:40 PM, Stephen Shaw via 4D_Tech <
>> [email protected]> wrote:
>>>> 
>>>> Hi all
>>>> 
>>>> I get an error when using the sql login command from 4D Developer from
>> a stand alone database, but not from a 4D client
>>>> 
>>>> 
>>>> SQL LOGIN(“4D:DatabaseName”;"user”;"Userpassword";*)
>>>> If (ok=1)
>>>>    ALERT("Success”) // works on 4d client attached to the database
>>>>    SQL LOGOUT
>>>> Else
>>>>    ALERT("Failure”)
>>>>   // fails with stand alone (error = SQL error 9918. Generic SQL
>> error [1006 SQL error 9918. Generic SQL error; 3 connection is broken])
>>>> End if
>>>> 
>>>> I have plenty (3) spare client licences available. Is this expected
>> behaviour or am I missing some subtlety
>>> 
>>> **********************************************************************
>>> 4D Internet Users Group (4D iNUG)
>>> FAQ:  http://lists.4d.com/faqnug.html
>>> Archive:  http://lists.4d.com/archives.html
>>> Options: https://lists.4d.com/mailman/options/4d_tech
>>> Unsub:  mailto:[email protected]
>>> **********************************************************************
>> 
>> **********************************************************************
>> 4D Internet Users Group (4D iNUG)
>> FAQ:  http://lists.4d.com/faqnug.html
>> Archive:  http://lists.4d.com/archives.html
>> Options: https://lists.4d.com/mailman/options/4d_tech
>> Unsub:  mailto:[email protected]
>> **********************************************************************
>> 
> 
> 
> 
> -- 
> -----------------------------------------------------------------------------------------
> Chuck Miller Voice: (617) 739-0306 Fax: (617) 232-1064
> Informed Solutions, Inc.
> Brookline, MA 02446 USA Registered 4D Developer
>      Providers of 4D, Sybase & SQL Server connectivity
>         http://www.informed-solutions.com
> -----------------------------------------------------------------------------------------
> This message and any attached documents contain information which may be
> confidential, subject to privilege or exempt from disclosure under
> applicable law.  These materials are intended only for the use of the
> intended recipient. If you are not the intended recipient of this
> transmission, you are hereby notified that any distribution, disclosure,
> printing, copying, storage, modification or the taking of any action in
> reliance upon this transmission is strictly prohibited.  Delivery of this
> message to any person other than the intended recipient shall not
> compromise or waive such confidentiality, privilege or exemption
> from disclosure as to this communication.
> **********************************************************************
> 4D Internet Users Group (4D iNUG)
> FAQ:  http://lists.4d.com/faqnug.html
> Archive:  http://lists.4d.com/archives.html
> Options: https://lists.4d.com/mailman/options/4d_tech
> Unsub:  mailto:[email protected]
> **********************************************************************


**********************************************************************
4D Internet Users Group (4D iNUG)
FAQ:  http://lists.4d.com/faqnug.html
Archive:  http://lists.4d.com/archives.html
Options: https://lists.4d.com/mailman/options/4d_tech
Unsub:  mailto:[email protected]
**********************************************************************

Reply via email to