Thank you for your post.
If you send a SQL statement through the ODBC driver, it may take some time to filter the information.
A better approach would be to edit through the shadow table instead of doing an Execute SQL since the link is already set.
If I have misunderstood what you are trying to accomplish, please let me know.
Thanks for your reply.
The problem is that editing through the shadow table can take a very long time for a large number of records.
What I am trying to accomplish is roughly the following. I have projects and materials. When a project is created, a subset of materials is assigned to the project (i.e., records are created in a separate assignment table with the project unique id) based on a flag in the materials record. Doing this the standard way through the shadow table takes many minutes. Shipping off an SQL statement to do it is almost instantaneous, except for the problem cited above. Even with my kludgey work-around, it takes maybe ten seconds.
By the way, I have verified that the problem is not in the MySQL database, where the changes take place immediately. I have verified this by sending a second SQL statement that counts the records in the assignment table and ships it back to FileMaker through another shadow table. That count is available in FileMaker immediately, and is correct. What takes a while is for FileMaker to recognize the new set of records added.
The problem is not that FileMaker takes a little bit of time, but rather that this is non-deterministic. If, for example, Refresh Window paused until all the records were recognized, that would be fine.