We are a group of users of Blackbaud products and are not affiliated with Blackbaud. We'd love to have you join our community to help and be helped in getting the most from your Blackbaud software.
Register now to join us to get independant advice on your system, connect with 3rd party consultants to help you maximize your database and have a real alternative to the official Blackbaud website.
Error when accessing or exporting matching gift records
We converted to 7.81.1334 revision 20 this morning. We have found a huge problem when accessing or exporting matching gift records. Here is the error:
General Error: [Microsoft][ODBC SQL Server Driver][SQL Server] Conversion failed when converting the varchar value '51556, 51558, 51560, 51564, 51566, 51569, 51571, 51573, 51577, 212892, 212894, 212896, 212898, 212900, 212902, 212904, 212906, 212908, 212910, 251205, 263128' to data type int native error: 245
In researching Knowledgebase, Blackbaud knows it's a problem. But this is the first I have heard of it. I have been monitoring this thread religiously and waiting to migrate until I felt all was well. Obviously I did not wait long enough.
Has anyone else encountered this problem? The error pops up even when you access the Gift tab for constituents who have matching gift records.
Thanks,
John
__________________ --
John W. Smith ('94, '98)
Associate Director for Advancement Services
Tennessee Technological University
931-372-6338 jwsmith@tntech.edu
I called support about this late Friday afternoon. The problem had already been reported and they are feverishly creating yet another patch to fix it. They said that it would be available late Friday or Today (Monday June 18th). I have not yet received an email from them about the patch.
HTH
So has everyone had issue's upgrading to 7.81? If this was released in Nov of 06 I have a hard time believing they are just working on this issue now????
I think this is a new error. We purposely waited to move to 7.81 to avoid initial bugs, so revision 20 was our first installation of 7.81. Evidently something broke between 19 and 20.
I know BB is diligently working to fix this.
John
__________________ --
John W. Smith ('94, '98)
Associate Director for Advancement Services
Tennessee Technological University
931-372-6338 jwsmith@tntech.edu
Do you think we should roll back to our older version (pre-patch) until they get this issue fixed or do you think the new patch will be available in the next day?