keep in mind also that an incomplete authentication method will reject the connection. the code should
1. explicitly call "change current user" and 2. return "true" http://doc.4d.com/4Dv16R4/4D/16-R4/On-SQL-Authentication-database-method.301-3316871.en.html in other words, an empty "on sql authentication" database method with no code would reject the connection. by contrast, if the database method does not exist, the connection is accepted. --- another factor to consider is that the ODBC driver version must match that of 4D. R releases have a different driver to .x releases. the architecture (32 or 64-bit) must match that of the client (Access) not 4D. http://doc.4d.com/4Dv16R4/4D/16-R4/4D-ODBC-Driver.100-3454244.en.html (the OP is about v13 so this point is probably irrelevant) --- finally, note that in v13 the full installer of 4D doesn't actually install the ODBC driver. rather, it installs the installer for ODBC driver (on Windows). > 2018/01/03 2:10、Chuck Miller via 4D_Tech <[email protected]> のメール： > If you put a trace in sql authentication method and see what happens. ********************************************************************** 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:[email protected] **********************************************************************
