We're using Windows 10 Pro v12, date of 9/6/23.
I got this FoxPro error while printing Unposted Contributions and also this week while I printed the Funds Report, as well. After clicking OK, the program aborts. I does eventually go through and I get the report. I think this error started after 9/6/23 program date
I did a Snipping Tool capture of the error but don't know how to put it into this topic.
Any ideas about this error? John
Microsoft Visual FoxPro error in Contributions
Moderators: Moderators, Tech Support
-
- Posts: 320
- Joined: Sun Sep 28, 2003 5:37 pm
- Location: First Cutlerville Christian Reformed Church
- Contact:
-
- Tech Support
- Posts: 3018
- Joined: Thu May 13, 2004 9:59 am
- Location: PowerChurch Software
- Contact:
Re: Microsoft Visual FoxPro error in Contributions
We will need to know what the error is. You can email your snip to support@powerchurch.com if you don't want to type the message out here
-
- Posts: 320
- Joined: Sun Sep 28, 2003 5:37 pm
- Location: First Cutlerville Christian Reformed Church
- Contact:
Re: Microsoft Visual FoxPro error in Contributions
Ill send it. Thanks. It's way too long.
-
- Posts: 320
- Joined: Sun Sep 28, 2003 5:37 pm
- Location: First Cutlerville Christian Reformed Church
- Contact:
Re: Microsoft Visual FoxPro error in Contributions
Around Sept 11, I emailed the FoxPro error I've been getting. Lately I've been getting this error again. Today I can't print the Funds Report. I've cleared the %temp% files according to your steps and even rebooted, to no avail. Usually doing these steps and rebooting works but not today.
Please advise.
John
Please advise.
John
-
- Tech Support
- Posts: 3018
- Joined: Thu May 13, 2004 9:59 am
- Location: PowerChurch Software
- Contact:
Re: Microsoft Visual FoxPro error in Contributions
As you said, clearing the temp folder will usually clear this error up. In doing a support search, there have been a few people that it didn't consistently fix. One thing they all had in common was Trend Micro antivirus/security software. If you have that installed and running on the computer where this is happening, try temporarily disabling that and run the report a few more times to see if that resolves the issue.