Hello, I don't think the statement (that "execute immediate" should only be used with the internal SQL db) was ever true.
the only restrictions that I know of are: no local variables with EXECUTE IMMEDIATE. https://doc.4d.com/4Dv17R5/4D/17-R5/Overview-of-SQL-Commands.300-4128371.en.html no ODBC in preemptive mode with Begin/End SQL some semantics: internal DB refers to the 4D database defined in the current structure file external DB refers to the 4D database opened via the SQL USE DATABASE command. it can be on the client or server side. https://doc.4d.com/4Dv17R5/4D/17-R5/USE-DATABASE.300-4142821.en.html a 4D database served by another 4D application is a "remote" database (not external). the "external" database referred to in the documentation https://doc.4d.com/4Dv17R5/4D/17-R5/EXECUTE-IMMEDIATE.300-4142833.en.html is not a remote database (that you would log into) but rather, a 4DB/4DD file you open via the SQL USE DATABASE command. note that there is not authentication required to use an external database. > 2019/08/15 3:41、William Swann via 4D_Tech <[email protected]>のメール: > > Now the question, is it still true that "execute immediate" should only > be used with the internal SQL db when using an entire SQL statement like > above in a text variable. ********************************************************************** 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] **********************************************************************
