Hi,
I regularly move my BE database between my desktop and my laptop (I have two licenses). I sometimes run into this irritating problem where the database will insist on trying to connect back to the other computer for some reason. That is, when I open it up, BE locks up while giving me a message that it is trying to connect to the other computer via AFP. When it fails (if the other computer is not on the network) then BE either permanently locks up or it simply doesn't allow me to use the database. I can work around it by double-clicking on the file itself, in which case it tries to connect to the other computer but does allow me to use the database once it fails to connect. My request is to fix BE so that files do not have this computer-specific dependency and the databases will simply run on whatever computer they are on. Otherwise, BE is working great for me. Keep up the good work!
Joe
bug when database file moved to another computer
I haven't run into anything like this (and I move databases between computers every day). And I can't think of what dependencies there might be -- the Bookends databases have no idea of what computer they are running on. Also, since you say it doesn't happen when you click on the database itself, just the app, how could Bookends even know the other computer exists?
I'm not saying you're not seeing a problem, just that I can't account for it by any code in Bookends.
If you want me to try to reproduce it with your database, contact me directly and we can see if I can.
Jon
Sonny Software
I'm not saying you're not seeing a problem, just that I can't account for it by any code in Bookends.
If you want me to try to reproduce it with your database, contact me directly and we can see if I can.
Jon
Sonny Software
will do!
It does indeed happen when I click on the database. It's just that if I double-click on it, it'll let me use it once it finishes looking for the other computer. If I start up BE in other ways (clicking on the application or using the "Goto Bookends" from the Word Tools menu then it won't let me use the database after looking for the other computer. I'll contact you directly about this. Thanks!
Joe
Joe
fixed (but still a problem)
It occurs to me that this most recent episode started after I directly access a BE database on my laptop over the network. I did a Clear Menu under the Open command and it fixed the problem. Apparently it was trying to open that database again. So I guess my request instead is to have BE handle this situation more gracefully. Even if it can't access the other BE database, it shouldn't keep one from using the main BE database. Actually, I'm not sure why it is even trying to open the other database but that's not a big issue. Thanks for the help!
Joe
Joe
OK, that makes more sense to me.
When you launch Bookends it tries to open the last-opened database. The problem isn't with Bookends, it's with the Finder (or at least Mac OS X) which isn't terribly smart about this sort of thing. It ties up the cpu until it times out (usually at 2 minutes).
It's possible I could work around this Mac OS X behavior -- I'll give it some thought.
Jon
Sonny Software
When you launch Bookends it tries to open the last-opened database. The problem isn't with Bookends, it's with the Finder (or at least Mac OS X) which isn't terribly smart about this sort of thing. It ties up the cpu until it times out (usually at 2 minutes).
It's possible I could work around this Mac OS X behavior -- I'll give it some thought.
Jon
Sonny Software
more info
Great! Just a little more info on the topic. Even after the time-out, I was still unable to use the main BE database unless I started BE by double-clicking the file (and not even then if I clicked on "cancel" on the box announcing that it was trying to access my laptop). So it's not just a matter of having to wait two minutes.
Thanks!
Joe
Thanks!
Joe
fixed!
It appears this problem was due to my Mac crashing at one point while having the second BE database open over the network. Apparently this left something out of whack. Clearing the database list fixed the problem and it hasn't come back. I thought this was a reoccurence of a problem that happened a lot to me some time back but apparently that old problem is fixed and this current one only happens under very special circumstances. Thanks Jon!
Joe
Joe