This version was an intermediate version issued to users who were affected by the two problems that were fixed in this release (most users did not need this update).

Project List

[Fixed] Users were unable to clone projects if their "live" data set resided within a Dropbox folder. An error occurred during the final append process after saving the new, cloned project. The error was caused by a locking process controlled by the Dropbox application.

Note: We do not recommend using a Dropbox folder as the permanent location of your data set unless you are the only user of FF&EZ and/or can guarantee that the database will never be opened on another system while still in active use on your system.

"In use" includes opening it on another system before Dropbox has updated your changed database files to its servers and then updated the shared files on the other system. This is especially likely if you use FF&EZ when you do not have an active internet connection. Allowing this to happen will result in multiple, "conflicted" versions of the database.

[Fixed] Version 4.2.009 did not correctly import projects from other FF&EZ systems if the following conditions were all true:

1. The incoming project was from FF&EZ version 4.2.xxx but earlier than version 4.2.011, and...
2. The incoming project included object Tags or specification IDs that were longer than the original 10 characters, and...
3. The first 10 characters of any longer object Tags were identical, or the first 10 characters of longer spec IDs were identical.

This problem did not affect any import functions from within the same FF&EZ database, only importing external projects from other FF&EZ systems. A symptom of the problem was receiving a message about finding "duplicate components" from the import process. This is part of an integrity check that normally fixes a rare problem in exported data, but which would cause a "false positive" under the conditions listed above.