Monthly Archives: March 2006

Documented Issues in FileMaker 8 v1 and v2

Fm8 Adv Box

According to FileMaker Inc., there are some significant issues in both FileMaker 8 v1 and v2. The company is working to release v3 soon which is expected to resolve the new issues introduced in v2. There is a good summary of the issues at the FileMaker Knowledge Base. It looks to me that you might be better off with the v1 release for the time being. If you are using FileMaker 8 or just about to start using it, you should read this yourself

There is one corruption issue in each of the versions which is my main concern. In v1, some batch operations and schema changes can corrupt indexes. Fortunately, those indexes can be easily rebuilt by turning the indexing on and off for that particular field with index problems. In v2, recovering a file corrupts the variable names in calculations. If you are using lots of variables, a new FileMaker 8 feature, you would want to check your variable names if you have to recover the file.

Developers might want to have a copy of both FileMaker 8 v1 and FileMaker 8 v2 around in case they want to switch between the two. For example, if you need to recover your file and you use variables a lot, you’ll want to be recovering with v1.

Anyone with more real world information about this is welcome to share it here in the comments. We will revisit this topic with an update when additional information is available or when v3 is released whichever comes first.

On a personal basis, I recommend Studio Manager customers use FileMaker 8 v1 until v3 is available. Neither of the two issues identified in v1 should present problems in Studio Manager. If you are customizing Studio Manager extensively, you should keep these issues in mind, however.

Knowledge Base article #5907 says this about the issues in v1:

  • Some calculations that require local client information (such as Get(WindowHeight)) are incorrectly calculated on the server. There are no known workarounds in this version.
  • Certain batch operations and schema changes might cause indexes to become corrupt. These indexes can be rebuilt via the Define Fields dialog box by turning the index off, and then on again.

Knowledge Base article #5907 says that “while FileMaker 8.0v2 addressed key problems in 8.0v1, it introduced some new issues”:

  • When using a FileMaker 8.0v2 product (Pro/Pro Advanced or Server/Server Advanced) as a host with clients prior to 8.0v2, performing find requests on unstored calculations result in all records being found. This is particularly dangerous when used in scripts that perform operations across the found set, such as replacing data or deleting records. To avoid this, make sure that all clients are using FileMaker Pro 8.0v2 or FileMaker Pro 8.0v2 Advanced. You may utilize the Get(ApplicationVersion) function to check the client version.
  • When using a FileMaker 8.0v2 product (Pro or Server) as a host, unstored calculations are always processed by the client application. In some network scenarios, this creates a significant decrease in performance, particularly when searching on these fields.
  • When printing from Windows based clients, layouts that use fixed margins will experience a shifting of the image by several pixels.
  • Recovering a file corrupts variable names in calculations.

Here is the advice from FileMaker Inc.:

During the period prior to this upcoming release, we recommend that you study the list of issues above carefully to best determine which version is right for you.

Technorati Tags: , ,