Second Database?

[emarino]

Our configuration is multiple workstations with a centralized database. When in the the office my laptop will use the central database, but can I create a local database for my laptop to be used away from the office? I would update it with a backup/restore from the central database. I recognize the risk of updating the central database from the laptop database, but on very rare occasions, I may also want to do this.

thanks,

Ed

[NeilZ]

Our configuration is multiple workstations with a centralized database. When in the the office my laptop will use the central database, but can I create a local database for my laptop to be used away from the office? I would update it with a backup/restore from the central database. I recognize the risk of updating the central database from the laptop database, but on very rare occasions, I may also want to do this.

thanks,

Ed

You would have to have a FULL copy of the Powerchurch program loaded on your laptop, then do a restore from a backup of the main database.

I would not select the default location during program installation, but create one that you would know is the copy of the database. Then I would change the label on the desktop icon to something other than Powerchurch, perhaps you may want to just change it to laptop copy. This way when you do plug in the laptop to the network, you would click on the networked Powerchurch icon to access that database.

That said. I would not do any updates to the database on the laptop, as during any restore process, you could overwrite changes made by someone in the office.

Quick question, why would you want to have a full database on the laptop when you're away from the office ??

[emarino]

So I would actually have two PowerChurch installations on my laptop--one that would point to the real database and one that would use the backup copy? You are right about doing updates--too risky.

As for the reason, I sometimes want the information in PowerChurch when I am away from the office. A remote connection would be ideal, but I don't think we can pull it off right now. Have you dealt with this situation?

thanks for the reply,

Ed

[NeilZ]

So I would actually have two PowerChurch installations on my laptop--one that would point to the real database and one that would use the backup copy? You are right about doing updates--too risky.

Exactly, although it would be only one full install, the other would be the link and setup to the networked database put there by the NetSetupX.EXE program.

As for the reason, I sometimes want the information in PowerChurch when I am away from the office. A remote connection would be ideal, but I don't think we can pull it off right now. Have you dealt with this situation?

thanks for the reply,

Ed

Depends on the information you need. At my last church we got the pastor a Palm PDA and used Pocket Powerchurch for that stuff.

[emarino]

Just want to make sure I've got it right:

The "real" installation is handled like our normal PowerChurch installation for a workstation, using NetSetupX.exe to point to the database.

The read-only installation is handled like a single system Powerchurch installation. It will install into its own folders and will create a local database. Then I would do a restore from the "real" database to repopulate the database. I should create a shortcut with a safe name so I know which installation I am running.

[NeilZ]

Just want to make sure I've got it right:

The "real" installation is handled like our normal PowerChurch installation for a workstation, using NetSetupX.exe to point to the database.

The read-only installation is handled like a single system Powerchurch installation. It will install into its own folders and will create a local database. Then I would do a restore from the "real" database to repopulate the database. I should create a shortcut with a safe name so I know which installation I am running.

Correct and correct. As I mentioned, I'd use a different default folder so that you're certain that there is no mixup.