POST TRANSFERRED FROM OLD FORUM
USER: Automated Workflows, LLC DATE: October 02, 2006, 08:08:25 AM
Thanks for your post.
This is actually a problem with FileMaker. With the release of FileMaker 7, I have noticed that, when importing large numbers of messages, FileMaker will sometimes stop responding to AppleScript commands. This causes the script to send a command to FileMaker and then wait for a response that never comes, eventually causing a timeout. Here are some suggestions for dealing with this issue. Make sure that you have the latest version of FileMaker 8, relaunch the solution and FileMaker prior to triggering a new import, and try importing smaller batches of messages at a time. I would also recommend making sure to set the solution to move messages to another folder after import. By doing this, if an error does occur, you'll be able to determine where it left off, and continue from there.
I have begun development on a new version of M2FMI, and I will continue to conduct testing of this issue, and see if there's anything that I can improve with regard to this issue for the next release.