Opening a file modified by 13 in v12 without hitting any 13-modified script or layout requires some careful work:
- being sure the file was last closed before hosting on a non-13 layout
- that there are no trigger or startup scripts from 13 in the file options or the default closing layout as well as any scripted layout changes which will be invoked during the login for the import.
- It's unclear exactly which things FMP13 and FMP12 attempt to change in a file during opening, but with it served on 13 the risks should be minimal as 12 should simply not recognize any 13-feature items, as opposed to 13 actually trying to modify some items which were written in 12.
Does anybody have any idea when FileMaker is going to fix the memory leak bug?
Well, for starters, has the bug been reported? If not, the answer to "When?" is "never". :-)
I was told by Filemaker that they are aware of the bug and do not need any more files for testing
Hayward Zwerling, M.D., FACP, FACE
ComChart Medical Software, www.ComChart.com
The Lowell Diabetes & Endocrine Center, www.DiabetesEndocrine.com
Vice Chair, MMS Committee for Information Technology
Does anybody know if the Software Update: FileMaker Pro 13.0v4 fixes the memory leak bug, which occurs when import large files with the FMS12 containers enabled?