Filemaker 12 is a version 01, speed complaints are common.
FileMaker 12 performance issues and experience
Now when FileMaker 12 is out and hot, many people are talking about its speed. Most of them are complaining, but that's not unusual. If you want to be responsible and serious player in the game, there is a good place to discuss all FileMaker performance issues.
Actually, there are two... ;-)
One is the FileMaker Optimizers group here on LinkedIn (http://24usw.com/infmop),
the other one is the Performance Tuning forum at the FileMaker Developer Community site (http://24usw.com/fmdevpt)
FileMaker Technical Network: FileMaker 12 speed issues & test results
This is the tab at the top of this page "Report an Issue"
OSX 10.7.4 is a few days old, sometimes doing an immediate update versus waiting a week or three can avoid problems.
A Safe Mode startup is easy to do and may help [ it runs an fsck (file system check) and repair and empties some caches]
Q: My system is 64-bit, are my FileMaker applications? Is there any benefit to running on a 64-bit system?
A: FileMaker is a 32-bit application, and will only run on 64-bit machines in a 32-bit compatibility mode. Because it is a 32-bit application, we will not take advantage of 64-bit benefits
FileMaker Pro and FileMaker Pro Advanced are 32-bit applications, and have not been thoroughly tested on 64bit Editions of Windows XP, Windows Vista, or Windows 7. If installed and run on a 64-bit operating system, they will run in a 32-bit compatibility mode.
FMS 12 amd FMSA 12 are listed as 64-bit http://en.wikipedia.org/wiki/FileMaker
Finding 32-bit vs 64-bit info was unreasonalbly difficult, links on filemaker.com ended in a 404 page several times.
Stalling is an issue I first experienced on a Windows 7 computer connected to a Remote database on a shared host.
It usually followed a number of impatient clicks creating a que for Filemaker to process. After a bit, I learned to just wait until Filemaker caught up.
It appears to happen on a local copy of FIlemaker 12 usually caused by an impatient multiple clicking.
The stalling can be avoided by a hands off one click only methodology. Sometimes we just have to wait for things to happen as a database is NOT an instant happening like video. Searches, sorts and other scripting can take time.
Filemaker does not have a thermometer to show the progress of our actions and it should.
Some times you can fake one during a long loop ( which takes a bit of time):
set counter to counter +1
if mod(counter;100) = 0
set thermometer image to div(counter;100)
I believe there is a thermometer for import and export and one for the Replace All.
@David and Jack.. Thanks for the excellent feedback, espically on a Holiday Sunday.