Hello, I do not use the Power church software, but im learning how touse it now. i am a tech hired to maintain the systems at a chuch in are area. We just replaced 5 systems at this location. They had WIN98 on a novell network and now are running WIN XP on a novell network. The PC version they are using is PC 8.5+ and is installed on a network server. after installing PC on the new systems they they can get around and veiw thing just fine they just get a error now when posting contributions and PC crashs. after it crashs a file is deleted. The file that is deleted it "Cotrans.dbf". after i do a restore of the file the indexing starts but i get a "Access denied" once it get to custon reports and crashs PC again. we then open PC up and see that the post entered even tho it crashed. just out of fun we went to a another WIN 98 system and installed PC on it. I had them do some posting and everything worked fine on tge win 98 system.
These people have full access to the network files and are administrators of thier system. NO firewalls are running.
here is the error that we get when we try to post
Program Frm_copost.DO_POST
Line 124
Error 1
Message: File 'f:\Pcplus85\Data\Cotrans.dbf" does not exist.
after that if we open PC up and try to do another contribution we get another error. I then look at the network share and see that the file has been deleted. I do a restore of the file and we start all over.
Is thier something i need to do with the WINXP system to get them to work with PC8.5+?
any ideas why the file get deleted every time we post a contribution on a WINXP system?
if more info is need i wil post it as soon as i can
Thanks for your time.
Joey
WINXP VS WIN98
Moderators: Moderators, Tech Support
-
- Program Development
- Posts: 463
- Joined: Fri Sep 05, 2003 3:08 pm
- Location: PowerChurch Software
- Contact:
Do you have the latest Novell client running on the XP systems? There might be some tweaks for "sharing", I am not a network specialist by any means, so I haven't any idea of where to look.
It might be related to the Novell drive cache not refreshing quickly enough for the timeout on the XP boxes. (just a guess here)
It might be related to the Novell drive cache not refreshing quickly enough for the timeout on the XP boxes. (just a guess here)
Tracy