tag:blogger.com,1999:blog-1869017312612730288.post9135444212324281798..comments2014-07-10T13:36:14.519+10:00Comments on The Grot's Blog: Doing a mass export of all data, using FileMaker’s native ExecuteSQL() function and a virtual table.Peterhttp://www.blogger.com/profile/11168876556656986735noreply@blogger.comBlogger2125tag:blogger.com,1999:blog-1869017312612730288.post-42302347709656044372014-07-10T13:36:14.519+10:002014-07-10T13:36:14.519+10:00Thanks for the pointer Karstyn, one of my colleagu...Thanks for the pointer Karstyn, one of my colleagues has done a lot with 360Works plugins but I haven't, and was not aware of that capability. Come to think of it, he might have not thought of it either ;-)Peterhttps://www.blogger.com/profile/11168876556656986735noreply@blogger.comtag:blogger.com,1999:blog-1869017312612730288.post-11988908314203299542014-07-10T12:45:19.767+10:002014-07-10T12:45:19.767+10:00Very nice!
I may have missed something in scannin...Very nice!<br /><br />I may have missed something in scanning the whole article, so my next comments may not apply. I have done very similar processes in the past, and if you would consider using a free plugin, ScriptMaster by 360Works, you may be able to simplify this even more.<br /><br />By just using the first SQL call to grab the data from each table as the value of a global variable, and then exporting that global variable with a function from ScriptMaster, the job is done. No need for a virtual table or all of the other processing and looping.<br /><br />However if you can't or don't want to use a plugin then my suggestion is a mute point! Anonymoushttps://www.blogger.com/profile/16531224492304915728noreply@blogger.com