AnsweredAssumed Answered

FM 12 Conversion Failure: Imcompatible with v11 solution

Question asked by BTimm on Mar 10, 2013
Latest reply on Mar 11, 2013 by BTimm


FM 12 Conversion Failure: Imcompatible with v11 solution


FileMaker Pro


12, updates up to date per March 2013

Operating system version

Windows 8 server, XP for Pro clients

Description of the issue

After conversion of legacy solution to version 12, I have encountered several critical bugs that are forcing decision to convert *back* to 11:

Key issues:

application stall and/or crash when creating new records.

application stall and/or crash when printing layouts and records.

Portal filtering not handling some calc functions.

I've spent a week chasing down various issues on these and other forums, followed some red herrings on file recovery, and generally have turned up more unresolved, open issue reports here and elsewhere, leading to more additional unknowns than solutions, and forcing my hand to roll back to version 11 for the foreseeable future until I can be confident future updates resolve core issues and allow me to update current solution and  handle legacy pre-12 conversions without unmanageable issues.

Steps to reproduce the problem

I'd be happy to send my files to any FM tech who would like to test and QA.

1) Attempt to create new record from native FM command, menu button or any scripted step. It seems core issue with the table, not isolated to any specific method.

FM will hourglass and more often than not crash the application.

2) Print command. Also not isolated to script step, can be reproduced from core command.

Expected result

Create new record.

Print records.

Actual result

Application crash.

Exact text of any error message(s) that appear

I have not found any windows log of application events but will continue looking.


None. Only logical workaround at this point is throwing in towel on 12 conversion and reverting back to 11. File in v11 has been stable. I did attempt a full recovery, data export and import, in v12, but the new, copied and cleaned file continued to fail on both accounts.