Hello Chuck & everyone,
One of my users is attempting to connect to 4D Server v13.6 from Access. He
has setup the ODBC driver which seems to work fine, entering a user name
and password and 'connecting' to 4d. However when trying to run a query or
open a 4D table in Access, he gets the following error:
ODBC--call failed.
Server rejected the connection:
00.202. OK
(#0)
Will creating an On SQL Authentication method solve this problem?
Thanks,
Alan
On Tue, Jun 6, 2017 at 2:57 PM, Charles Miller via 4D_Tech <
4d_tech@lists.4d.com> wrote:
> You should also have an on sql connection method with log in info
>
> we have code that looks like the following
>
> *SET QUERY DESTINATION*(Into current selection)
>
> *Case of *
>
>
> *: *(*User in group*(ONSQLAuthenUser_txt;" "))
>
> *CHANGE CURRENT USER*("SQL_ReadOnly";"12345")
>
> *: *(*User in group*(ONSQLAuthenUser_txt;"ReadOnly"))
>
> *CHANGE CURRENT USER*(ONSQLAuthenUser_txt;ONSQLAuthUserPW_txt)
>
> *: *(*User in group*(ONSQLAuthenUser_txt;"ReadWrite"))
>
> *CHANGE CURRENT USER*(ONSQLAuthenUser_txt;ONSQLAuthUserPW_txt)
>
> *Else *
>
> *If *(*Not*(*User in group*(ONSQLAuthenUser_txt;"ActiveUsers")))
>
> *C_LONGINT*($Processid_l)
>
> $Processid_l:=*New process*
> ("ut_LogExternalConnects";128*1024;"ONSQLAuthenticate";
> ONSQLAuthenUser_txt;
> ONSQLAuthenIP_txt;ONSQLAuthUserPW_txt;"InactiveUser")
>
> *Else *
>
>
> *End if *
>
> SQL_ConnectionOK_b:=*False*
>
> *End case *
>
> *$0*:=SQL_ConnectionOK_b
>
> *ON ERR CALL*("")
>
>
> Regards
>
>
> Chuck
>
> On Tue, Jun 6, 2017 at 2:53 PM, Timothy Penner via 4D_Tech <
> 4d_tech@lists.4d.com> wrote:
>
> > Hi Bob,
> >
> > > This is the source of confusion, from the 4D Design Ref (v15), talking
> > abtout setting types of access to schemas:
> > > "More specifically, if you only assign Read Only type access to one
> > group this will not have any effect since this group as well as all the
> > others will continue to benefit from Read/Write access (assigned to
> > <Everybody> by default). In order to set a Read Only type access, you
> also
> > need to configure the Read/Write access."
> > > I"m not clear at all about why "this will not have any effect...")
> >
> > Let's say you have a group named Group1.
> > If you assign Group1 to READ ONLY for this Schema, but leave <Everybody>
> > set to Read/Write access, then Group1 would effectively get Read/Write
> > access because they are included in the Everybody pseudo-group.
> > That is what is meant by the READ ONLY setting would have no effect.
> > If you want Group1 to be READ ONLY then you need to also check the
> > READ/WRITE group to be sure they do not have access.
> >
> > Another way to look at it, is let's assume you have User1 who belongs to
> > both Group1 and Group2.
> > Then you assign Group1 to READ ONLY and Group2 to READ/WRITE for the
> > schema applied to this table.
> > Then you login as User1 whom belongs to both Group1 and Group2.
> > In this situation the User1 would have READ/WRITE.
> >
> > This tech note is a bit old but it may help explain the use of Schemas:
> > http://kb.4d.com/assetid=51814
> >
> > -Tim
> >
> >
> >
> > **********************************************************************
> > 4D Internet Users Group (4D iNUG)
> > FAQ: http://lists.4d.com/faqnug.html
> > Archive: http://lists.4d.com/archives.html
> > Options: http://lists.4d.com/mailman/options/4d_tech
> > Unsub: mailto:4d_tech-unsubscr...@lists.4d.com
> > **********************************************************************
>
>
>
>
> --
> ------------------------------------------------------------
> -----------------------------
> 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 Sever 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: http://lists.4d.com/mailman/options/4d_tech
> Unsub: mailto:4d_tech-unsubscr...@lists.4d.com
> **********************************************************************
>
**********************************************************************
4D Internet Users Group (4D iNUG)
FAQ: http://lists.4d.com/faqnug.html
Archive: http://lists.4d.com/archives.html
Options: http://lists.4d.com/mailman/options/4d_tech
Unsub: mailto:4d_tech-unsubscr...@lists.4d.com
**********************************************************************
