Do you have any scripts that run when the file is opened?
Is the file hosted over a network?
What do you see just before the file "hangs"? Hourglass, coffe cup, lightning bolt, or ....?
Does the "other computer" that opens the file successfully also have Mac OS 10.5 installed or a different OS and/or version?
Here are the answers to your quesions:
Yes, I have a script that runs when the file is opened.
Yes, It is hosted over a network, but I tried to open a copy of it and that did not work.
I see the spinning ball. When I force quit and look at the report it says "hang".
The other computer that can open the database is running 10.4
Later today I am going to reboot from another hard drive that has a back up of the system which was created earlier than the system I am having problems with. I suspect that it will work fine, but can't be sure until I do it.
Thanks again - Sam
Now for some inexplicable reason I can open the database from my computer and from the network.
I'd take a look at the script that runs when the file is opened and what layout's are referenced during opening.
It could be that your file is attempting to run a series of calculations needed to update some summary fields. If this is done while all or most of the records are in the found set, you'll get a major delay in opening. These fields could be referenced by the script or be present on the layout that is current at the time the file opens.
Likewise, certain sorts and finds can trigger major delays in large files if they involve large numbers of records and unstored/unindexed fields.
The cause could be something else, but that's what I'd check first.
Thanks Phil, I will look it to that.