1. Yes, INCREASE. Sorry, that's what I meant.
2. Yes, this could be done. I could certainly do it in my sample FileMaker database, which is provided with M2FMI. This would add a bit more to the configuration requirements, however. In addition, it would add complexity for people that want to use their own database, especially those who aren't FMP experts.
3. Again, importing attachment data into the container field is a limitation of FileMaker's AppleScript support (I haven't checked FMP 10 yet), and not of M2FMI itself. To do it, I'd need to come up with a fairly involved workaround, which would include saving the attachments somewhere, renaming them, triggering a FileMaker script to perform the import, and then cleaning up once the import is complete. Not the most elegant solution.
In any case, again, attachment importing is on my list, and I will try to provide support for this in the future. In the meantime, if you're interested in discussing the possibility of hiring us to develop a custom solution for you, please feel free to submit a consultation request via our website at http://www.automatedworkflows.com/contact/requestconsult.html
Thanks again for your feedback.