We have a similar situation, but it's simply because we don't want to have to install the ODBC on every Client.
The way I get around this is to separate the SQL query into it's own method, and have it run on the Server. This way there is only 1 ODBC System DSN. The method packs the results into an Object (JSON format) and returns the results back to the Client method, where it is unpacked and displayed to the user. Hope that helps! Best, Steve ********************************************* Stephen J. Orth The Aquila Group, Inc. Office: (608) 834-9213 P.O. Box 690 Mobile: (608) 347-6447 Sun Prairie, WI 53590 E-Mail: [email protected] ********************************************* -----Original Message----- From: 4D_Tech <[email protected]> On Behalf Of msherloc via 4D_Tech Sent: Wednesday, April 10, 2019 6:35 PM To: [email protected] Cc: msherloc <[email protected]> Subject: How to connect to a 4d ODBC server across a network I am accessing (via an SQL query) my 4D database across a network. The 4d ODBC database is situated on one server and the software I will be querying the database will be on another server. Is it possible to create a UserDSN or SystemDSN that can find the server located across the network?? Not sure how to do his and keen for some advice -- Sent from: http://4d.1045681.n5.nabble.com/4D-Tech-f1376241.html ********************************************************************** 4D Internet Users Group (4D iNUG) 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) Archive: http://lists.4d.com/archives.html Options: https://lists.4d.com/mailman/options/4d_tech Unsub: mailto:[email protected] **********************************************************************
