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