User Support Forum

If I run the "Family Update Form" report more than once the program crashes. I get the windows box that states "PowerChurch Plus has encountered a problem and needs to close." When I open PowerChurch Plus again, I can run the report once, sometimes twice and then it crashes again. Occasionally, I have to reboot the whole system to get it to run. I am using Windows XP Pro 2002 Service Pack 3.

Blessings,
Shelley

Shelley wrote:If I run the "Family Update Form" report more than once the program crashes. I get the windows box that states "PowerChurch Plus has encountered a problem and needs to close." When I open PowerChurch Plus again, I can run the report once, sometimes twice and then it crashes again. Occasionally, I have to reboot the whole system to get it to run. I am using Windows XP Pro 2002 Service Pack 3.

Blessings,
Shelley

Does it give any other indication other than that "Powerchurch Plus ... needs to close." ?? Any sort of diagnostic information like "Module PrintSomething, Line #25 .... " ??

Also, are you printing to a local printer, or something on the network ??

If this is a Visual FoxPro error message, there should be an error log file created on your system. To be able to properly diagnose this problem, please send an e-mail to support@powerchurch.com and attach the following file:

C:\Program Files\Common Files\Microsoft Shared\VFP\vfp9error.log

If you have a problem doing this, you can give us a call in support at (800) 486-1800

Sorry for the delay in responding. I got swamped. No other error message. Not printing, just preview on screen.

• Select Family Update Form
  Choose criteria for report
  Watch the blue percent bar preparing data...reaches 100%.
  Report Preview Screen pops up white, waiting to be populated.
  Crash. No error message. Just the Windows box indicating PowerChurch Plus has encountered a problem and needs to close."

Zorak, I will see what I can to to get you the information requested.

Blessings

I am able to reproduce this problem but am unable to narrow down the cause. If I do not make any selections - in other words I query the entire database - it crashes. If I narrow down the selections it does not crash. I do not have a file vfp9error.log listed in the folder listed by Zorak or anywhere else on my computer. If I select a range of names and just use last names ranging from "a" to "z" it crashes, if I list actual last names names in the a to z range it works.

That's odd. I have two sets of testing data here, one with 15 families and one with over 4500 profiles and can not get this to happen with either set. The report does take a very long time for the 4500 profiles setup, but I can't get it to error.

We will get this written up to see if there is something that can be rearranged, or we may come back here and ask for data from one of you to try and recreate the problem.

Here is some interesting information. I do not seem to have the problem on my Windows 7 machine networked to the same data as my home XP machine which is having the problem. I also don't seem to have the problem on the church computer also running on XP. I new the data on the church machine was a little different so I did a backup and then loaded the backup on my home machine and the report worked the first time but crashed when I tried it again. Thought it might have had something to do with the reindexing so I reindexed and the crash still occurred. I then went to load the backup again but mistakenly did a backup instead and again the first attempt to run the report worked and the second attempted failed. So if I do a backup or reload a backup the report works the first time only. It is unique to this one machine however. Even after the crash on my XP machine the report still works on the Windows 7 machine networked to the same data and doing nothing to the XP machine. The machine that crashes is a Dell Dim3000 using XP Home Addition Version 2002 Service Pack 3 with Pentium 4 CPU at 2.8GHz and 2 gig of ram. Very interesting problem.

Wow. I feel useless to provide anything coherent or useful. All I can add is it doesn't seem to matter what kind or how many selections I make, I crash. Doesn't seem to be a pattern to it all.

Shelley

I haven't been able to reproduce this.
Since tborgal is unable to reproduce the problem with the same data on some machines, yet able to on another, I am suspecting there is a common workstation configuration.

For both, Shelley and tborgal
What type of software is running in the system tray (the icons next to the clock on the task bar)?
What anti-virus suites are or have been installed on the system?
What printers do you have installed? Which is the default printer?

Requested information from the machine that is crashing.

The following items are in my system tray:
Seagate external backup drive
Ad-Aware
NVidia Settings
Mouse
Norton Security Suite (all three machines I tested are using this anti-virus program and version)

Printers:
Broderbund PDF Creator
Epson Stylus Photo R2400
HP Officejet 6500 Series fax
Microsoft Office document Image Writer
Quicken PDF Printer
DoPDF v6 (this is on all three machines)
HP Officejet 6500 printer (default) (this is on both of my home machines)
Microsoft XPS document writer

Is the HP OfficeJet 6500 Printer a network printer on one of the two machines? Is it the default printer on both workstations?

It is a networked printer setup as a standard TCP/IP port on both machines and is the default on both machines.

After scrolling up and re-reading your post. You have an XP and Windows 7 box at home. The XP box at home is giving you the problem.
If you

• close PowerChurch
• change the default printer to one of the PDF printers
• start PowerChurch

Can you reproduce the error?

After making the change the problem has changed a little. It now does not seem to crash if I do not make any selections, but it does crash if I enter an "a" and a "z" in the last name fields. It also now crashes if I enter full last names.

Retraction. After more testing the problem is still there even if I don't make any selections. Even tried a different PDF printer with the same result.

Does this happen when you bring the report to the screen, and click the "Restart with same parameters" button? Or by printing it multiple times? Or restarting it after closing the report?