We are having a HUGE problem with the Project Detail Reports. We recently upgraded to SQL 2005 and FE 7.70.638.0011. Immediately after our Project Detail Reports were running very slowly or getting hung up or whatever. I have contacted support a number of times with no viable response. Has this happened to others? If so, have you found a resolution? These reports are critical to daily operations and I am not sure how much longer I can keep the wovles away from the front door...Thanks for any help! Nora Langolf Community Foundation for the Fox Valley Region Appleton WI

We are also having problems with slow reports/no reports. The Project Summary Reports are the worst. I haven't been able to get this report out correctly for almost two weeks. BB response is that it is our computer and that we need to purge files, etc in our computer. I was able to run the reports before. The BB response is off-base, as we happened to have a new computer, and guess what--we still can not run this report.

I'm hopeful that Blackbaud management will decide to take a long hard look at their current business model in the context of how they address issues such as this. It's disconcerting when payroll modules don't work properly, the eRequisitions module is completed ignored and good faith efforts to assist Blackbaud in addressing these problems - by a group of savvy users I might add - are largely ignored. David Stephens Chief Financial Officer Martin Methodist College

Anyone having problems matching the the ending balances in previous year to the beginning balance for the next period using transaction codes within a project number? I was able to run this report for previous months without any problems. I've been working with BB. They suggested upgrading to the most current version and load the patches to this version [13]. I have done this....still does not work. I'm now trying to figure it out on my own.

Although we limit postings from the forum administrator, we want to respond to the comments posted by David, Marion, and Nora. We are aware of the Project Detail Report processing slowly when using SQL Server 2005 and are currently working to resolve this issue. We apologize for any inconvenience. This information is also in Knowledgebase (BB387236). In reference to Payroll 7, we have dedicated a majority of our resources over the past 18 months to improve quality and customer satisfaction. The feedback received from payroll 7.70 beta customers was positive and reflected an overall improvement in the product. A separate team of designers and programmers is dedicated to improving the quality and usability of eRequisitions using customer suggestions and feedback. This team has also met with several customers to discuss organizational procedures, recommended changes, and to identify the key areas for improvement including the approval flow process and product catalogues. The new version of eRequisitions is scheduled to be released in 2008.

I have had a similar problem with beg balance on income statements. It runs fine at one time and then the beg bal was corrupted from an update. The solution was to rebuild the VCO. This is a painless procedure. Here is the email from Blackbaud I found most useful. (We discussed how updates on non-Blackbaud products on the server may affect your database during our call today. Since you have reported having to recreate several aspects of the software, I may have a way to cut down on this frustration. If your IT department is performing any non-Blackbaud update, you may want to try to detach the database during this process. This way the database is not actively running. At times, I have seen non-Blackbaud updates to the server, corrupt tables on the back end of the system. If your IT department is performing Blackbaud updates, please keep the database attached as the update will not be successful. In addition if you see a report that uses a VCO all of a sudden show incorrect information, please use the following troubleshooting steps to make sure corruption is not the cause. 1. Recreate the report template 2. Recreate the VCO, validate it, and run the new report on that VCO. 3. Check your date ranges for accuracy.)From Blackbaud Support My IT staff didn't feel that the upgrade was affected by other nonblackbaud upgrades because our Blackbaud applications are on a separate server. However, rebuilding the VCO fixed my beg bal issue. Hope this helps, Connie Connie W. Jones, CPA Wesleyan College 4760 Forsyth Road Macon, GA 31210 Phone: 478-757-5175 Fax: 478-757-3902 Connie Jones Wesleyan College Dir of Compliance 478-757-5175

I am now having issues with fund balance rollover regarding fiscal 2005-2006 to fiscal year 2006-2007. Ending balances from that prior year-June 30, 2006 and beginning balance carried over to the next year-July 1, 2006 are not agreeing on the Project activity detail report. We just loaded the patch 14 on Friday, and now I am seeing issues with my reports. Anyone else having a problem?? Marion Katsereles, University of MD College Park Fdn. University of MD College Park Fdn College Park, MD 20742

We have had the same problem, and i have revised the vco without it correcting the problem.It seems to me that Blackbaud should give detailed instructions on how to correct the fund balance rollover problem at the project level from fy2006 to FY2007.On the account code level, fund balance is correct, but we need to have a trail on the project level for what we are reporting to the projects.

Question This is for the Project Activity Detail report, not a report that I run using the VCO. My financial statements appear to be running correctly using VCO. From what I see, the problem started when we applied the last patch. Marion Katsereles

Re: Project Activity reports I had problems with ending balances and beginning balances crossing fiscal years involving T-codes. The ending balances were not rolling forward to the new fiscal year. One customer support analyst was very helpful in pin-pointing the problem. Under Configuration/funds a specific T-code needed to be check marked for "Preserve Details During Close." This was done through Admin/Update Fund Transaction Requirements." Be sure to have back-up data prior to performing this. Hope this points you in the right direction.

My projects and t-codes are not checked to preserve balances. I am told that if I run the "update fund requirement utility" now that the process will overwrite existing projects with the default project (Solution number BB59282). So I will have to manually record the balances in accounts allocated to those projects. Ouch! I haven't closed last year nor have I run the update that seemed to have affected so many negatively. Gee... I wish I had of checked this box on installation before I had transactions attached to projects. It wasn't even discussed as an option during installation. Still reviewing and studying my options.... I only use Allocatin Manager for project management so I can afford to drag my feet for a short while. Connie Jones Wesleyan College Dir of Compliance 478-757-5175

This is what seemed to take place in our system. When the fiscal year is pre-closed, the ending T-code balances did not roll forward to the new fiscal year [zero beginning balances appeared for the new fiscal year]. The "update fund requirement utility" did not affect historical transactions. Beginning T-code balances need to be manually entered through journal entries. We shall see what happens when FY08 is closed next year..... Note: Project balances have always been okay due to projects check marked to "preserve balances"...its just the T-code balances that have been affected.

When we first set up FE about 4 years ago, we had the same problem. That box wasn't checked. Blackbaud ended up taking our database unposting all of our journal entries, checking the box and then reposting the journal entries. If this didn't happen we would have been in a world of hurt. I would suggest that you contact Blackbaud and demand that they fix it. Especially since you were not told during installation. Kathleen Patlovich Boise State University

Very helpful posting Kathleen. Many thanks, I will pursue this. Connie Jones Wesleyan College Dir of Compliance 478-757-5175