Piotr

Believe me, it does (albeit only in a Trailing Grand Summary viewed in the View as List). This horrible "feature" is even mentioned in the FM 10 help: "When you view summary data in Table View: [...] - FileMaker Pro automatically adds field labels (such as Total) to subsummary parts to identify the data displayed."

I have a fairly straightforward table (i.e., records appear as a table in View as Table) that sums up numbers in fields using summary fields. The summary fields are placed in the Trailing Grand Summary. In View as List the summary fields display just the numbers that are the sums of values in the displayed records. Unfortunately, in View as Table each summary field is preceded by the word "Total:". Because each column of numbers is very narrow, the printout of the table shows only the words "Total" (or a fraction of it) instead of the actual numbers. I am fully aware that I can resize the width of each column and make the full "Total: XX.X" appear, but this ruins the entire printout. I also need to use a Trailing summary instead of the Footer because footers do not slide up when printing. I understand the reason why FIleMaker Inc. decided to add the word indicating what kind of a summary field it is (total, average etc.), but please, please let the user decide whether to display it or not. Does anyone know if it is possible to display just numbers (without the "helpful" explanation of what these numbers mean) in the Trailing Grand Summary in the View as Table?

I just discovered that during the creation of a stand alone FM application using the Developer Utilities all links to external data sources (other FM files) get stripped of their extensions. Thus, if the path used to be: file:old_data/Address.fp7 it becomes: file:old_data/Address Naturally, any script that requires the file Address.fp7 fails. To me this is a major, extremely serious bug that destroys the functionality of my stand alone solutions. Does anybody know a workaround?

Once again FileMaker fails to fix a serious bug that consistently causes a crash of the application. In the Windows version of FileMaker versions 6 to 9 importing a sound file (.aif, .wav) into the container field invariably causes a crash (a conflict with QuickTime for Windows.) It boggles the mind that FM Inc. still has not fixed this annoying, dangerous, and well-documented bug. Shame on you, FileMaker Inc. :)

New Millennium makes the Media Manager plugin that addresses the QT crash issue. Here is the link: http://www.newmillennium.com/index.php?submenu=Developer_Software_MediaManager&src=directory&view=products&srctype=display&id=5&category=Developer%20Software Look for the section "MediaManager Solves the QuickTime 7/FileMaker Pro Bugs on Windows" at the bottom of the page. Piotr

The bug in FM for Windows that causes it to crash when trying to play an imported .AIF file is still there. I can't believe that this OLD bug (since v. 6) has not been fixed yet. There is already a plug-in available that allows you to import sound files without relying on FM and QuickTime engines, developed specifically to address this bug. Shame on you FileMaker Inc.! Piotr

The annoying crash while trying to play or import a sound file into a container field persists even after updating to QT 7.1. I wish Apple would get its act together and finally fix it! They are clearly aware of the problem, at least according to the Windows Crash Analysis: "The error was likely caused by QuickTime Player. This software was created by Apple Computer, Inc.. Microsoft has researched this problem with Apple Computer, Inc., and they do not currently have a specific solution for the problem that you reported. For help on QuickTime Player, visit the following Apple Computer, Inc. support site."

Yesterday I updated FM 8 on two machines running Windows XP Pro to v.03. Since then I already experienced 3 instances of the application freezing ("FM not responding" in Windows Task Manager), forcing me to force quit it (and lose recent changes in scripts.) This happened on several different files, and under slightly different circumstances. In one case the feeze occurred when looking at the table structure, in two other cases while editing scripts. Has anybody else experience this annoying and dangerous behavior?

Unfortunately, PS MediaPlayer plugin would solve nothing because it requires QuickTime to run. Besides, why should I pay for a feature that I already paid for by buying FileMaker. Apple is clearly doing something wrong if two of their flagship products (ableit FM is now considered a separate company, owned by Apple) cannot coexist.

FileMaker 8 Adv. and QuickTime (versions 6.5.2 and up) are not compatible with File Maker on Windows XP. Importing a sound (.aif) into a container field and a subsequent attempt to play it results in a crash of FM. The situation is particularly severe with QT 7. With QT 6 the crash does not happen every time I attempt to play the sound, whereas with QT 7 the crash happens every time I try to play the sound. If the first layout of an opening database contains a sound field the crash occurs right at the startup of FM. I tested it on 3 separate Windows machines (both XP Home and Pro), with many different databases and sound files. Did anybody encounter and knows a workaround to this issue? For me this bug may spell the end of my relationship with FileMaker (I have been using it since v. 2.0), and force me to move to a different database environment - my databases are databases of biological sound recordings, some containing up to 30,000 sound records.

In FM7 all "Status" functions have been replaced by "Get". Unfortunately, the change of the name also brought in a diminished capacity of some of these functions. Previously, the function "Status(CurrentFoundCount)" produced results that could be seen in related files. Now it is impossible: related files do not display the values in the field "Get(FoundCount)" of other files. Am I missing something, is there another way to display the number of currently found records in a related file (NOT another table within the same file)?

OK, I should have researched it more before posting - the Exit Record is now replaced by Commit Record (which does more than just exit a field). Still, it would be helpful of FM to include this information in the Help.

The "Exit Record/Request" script step is gone in FM7. It probably has to do with the new way files can be selectively saved. This is fine, but how do I now exit a field? I need a step that will leave a field without going to another one. What should I use? Interstingly, the FM7 Help files still refers to this non-existent step (excerpt: [...]Make sure that the record you want to delete is active (use navigation script steps), and then use Delete Record/Request. If the current layout contains a portal, use Exit Record/Request to make sure that no related record is selected, then use Delete Record/Request.[...])

Hmmm, I always thought that comparison operators that compare two values and return either True or False make a Boolean statement. The only difference in this case is that True = "empty" and False = "not empty". Please correct me if I'm wrong.

Thank you Ender for your constructive reply. You missed the point completely: the issue is not that I am too lazy to fix my calculations, the issue is that the Boolean statements in FM7 give FALSE results. I am not going to migrate to the new version until this bug is fixed.