Networking performance

[tmstone835]

I have read through many of your FAQs and forum topics and would like some clarification regarding a network installation of PowerChurch.

When we install to a network mapped drive we then need to run the netsetup program on each workstation. This seems to only install a small subset of runtime files in order to access the shared data. I found another topic in the forum where the person was talking about using a VPN. You recommended doing a local installation on the workstation and then just changing the pointer to the mapped network drive where the data is located.

It seems as though we would get a faster local running copy if we install the full version that only has to get data across the network rather than using the recommended installation of using the runtime files on the local workstation.

My questions are these:

1. Is the runtime installation putting all of the needed program files on the local computer or does that installation cause the local workstation to access executable code from the server?

2. If we do a local installation and just point the data directory to the server's data drive, is the program aware of file locking issues and are their other items we need to know about such as security?

[Tracy]

1. The Version 11 NetSetup will install a starter application that will automatically download the latest executable from the network install you keep updated. Version 10 can determine when running a local copy, if the network copy is not the same. The local user is informed of the condition, yet allowed to continue to work with the program. Prior versions do not have any warning in place.

2. File locking is managed by the program. Security inside PowerChurch and via the network administration is useful. PowerChurch needs write access to the PCPLUS?? folder and all folders under it.
Write Cache will most likely cause data corruption. This is a policy on the disk of the server system.