I sometimes work on my Calendar database on one of a few different computers. The database “lives” on Peter Pan so I will usually just screen share with Peter Pan so that I’m in fact working on the computer where the database lives. Sometimes however someone else needs Peter Pan, so it’s convenient to load the database into memory via WiFi onto Wendy and just save the data via WiFi back to Peter Pan every so often.
When I did that yesterday, though, my saved data disappeared. I think it’s because I still had the Calendar database open on Peter Pan and I apparently saved the old data from Peter Pan on top of the new data that had been saved from Wendy.
So I think my question is, what’s the best way to make sure only one computer has access to that data at any one time, without making the major jump into the Panorama Server? It seems like there used to be a way to lock a database or something? Other ideas?
I’m not seeing that this makes any sense. Because Peter Pan is not a server, how are you believing that you are ‘saving the data back to Peter Pan’? If you are working on Wendy, you are saving to Wendy. Only closing the copy on Peter Pan, and then doing a Save As onto Peter Pan and replacing the copy on Peter Pan would accomplish your need. And I’m not hearing that as your procedure.
Correct, that is not my procedure. Instead, I mount Peter Pan’s disk on Wendy, and then on Wendy I double-click the Peter Pan file so that it opens in the Panorama application that is currently running on Wendy. Thus, I can edit the original data without needing to make a copy of it on Wendy.
I agree with Bruce, you should be using a shared database via Panorama Server. I disagree with your assertion that it is a “major jump”. That was possibly true back in the Panorama 5.5/6.0 days, but not now. Yes, there is some modest extra expense, but if you’re running an organization it shouldn’t be major.