Here is the crash report...
Date/Time: 2009-10-14 22:09:56.780 -0700
OS Version: 10.4.11 (Build 8S2167)
Report Version: 4
Command: FileMaker Pro
Path: /Applications/FileMaker Pro 8.5 Advanced/FileMaker Pro Advanced.app/Contents/MacOS/FileMaker Pro
Parent: WindowServer 
Version: FileMaker Pro Advanced version 8.5v1 (8.5.1)
Exception: EXC_BAD_ACCESS (0x0001)
Codes: KERN_PROTECTION_FAILURE (0x0002) at 0x00000000
Thread 0 Crashed:
0 com.apple.CoreFoundation 0x9082063c CFDictionaryGetValue + 17
1 com.dracoventions.gap_filler 0x1b831466 CAESEncRegKey::ReadData(unsigned char*&, unsigned long&, unsigned long) + 130
2 com.dracoventions.gap_filler 0x1b839986 GFPrefs::LoadAll() + 180
3 com.dracoventions.gap_filler 0x1b82b8df ScheduledTask::ScheduledTask[in-charge](ScheduledTask::TaskType, unsigned long) + 721
4 com.dracoventions.gap_filler 0x1b82f34f FMExternCallProc + 181
5 ...ilemaker.dbengine.framework 0x01d38a76 Draco::DBPlugIn::SetEnabled(bool) + 374
6 com.filemaker.pro85A 0x001bbbe3 CFMProApp::InitInstance() + 935
7 com.filemaker.pro85A 0x00031da7 CMacApp::Main() + 39
8 com.filemaker.pro85A 0x001b93d9 main + 33
9 com.filemaker.pro85A 0x00003272 _start + 228
10 com.filemaker.pro85A 0x0000318d start + 41
Which lead me to delete the extension called gap filler (which was no t installed in the other user accounts) and VOILA - no more crashing. Not sure why it would now choose to screw up but I do not care....
Thank you for your posts.
Since you are running Mac OS X 10.4.11, the preference file is located:
User Account -> Library -> Preference -> com.filemaker.*
Try removing that file. When FileMaker Pro launches, it looks for this file, and if it doesn't find it, a new one is created.
The preference file should not cause a crash, so I don't have much hope this is going to help. It very well could be a corrupt User Account. Try running Apple's utility "Disk Utility", and repair disk permissions.
Please keep me updated with any progress.
Hey TSgal.. I think you missed my Issue resolved conclusion:
it was a misbehaving FileMaker Extension called Gap Filler. It was installed on one user acct and not the others that was the difference. Once Removed the problem was gone.