I would look into Office 365. MS will store Sharepoint in "the cloud" (expressing hatred for that term), and you will pay a subscription fee for it. Might be a lot cheaper than trying to keep extra hardware around for SP

That said, as long as you have licenses to Sharepoint (both the Sharepoint license and the Client-Access-Licenses for people using it), should should be able to copy and put onto another server.
Read More...

I don't think it's a problem with the table reference as much as that the records would be updated, which would kill the "point-in-time"-ness of the original static query.
Read More...

Yes, actually. So if you go to properties of the query, look for System Record ID.

The table will be STATIC_RECS_[System Record ID]
Read More...

I believe that static queries are built under the tmp****** table structure on the SQL end. So when you create a static query I believe it adds a new one of those tables.

There *is* a way to do it but if that's not it, then there is a table somewhere with query number and ID.
Read More...

BBDM is designed for you to bring in rented lists into a secondary system, and for you to use the Finder Number (which you could scan in), which would bring in the Name and Address into RE - so you might be referring to the use of barcodes in the BBDM context.

The code to scan encoded with all of that information would be massive! I used to encode Campaign/Appeal/Package into a special way that wasn't Blackbaud's design, so basically we had plaintext IDs and tab characters (I believe are $I i
Read More...

Constituent Query:

Summary -> Gift Summary
# of Gifts: 0
Criteria: Appeals (any except the one)

AND

Summary -> Gift Summary
# of Gifts: >= 1
Criteria: The one appeal

This will give you a list of people who ONLY gave to that appeal. Then you can merge it out.
Read More...

What version of RE are you using?
Are these PDFs, and if so, what version of Adobe Acrobat are you using?

You could try running RE as administrator to see if that fixes things.
Read More...

We used Cornerstone way back in the day at the place I used to work - was probably 5-6 years ago now since I last used it. They were for a walk event.

From what I remember, the data was incredibly hard to work with. However, things may have changed a lot since then.
Read More...

I have indeed seen this before but I cannot remember for the life of me how it was resolved.

Possibilities:
-If you have SQL Server Management Studio, you may want to see what user is running the jobs (The BMC merely creates its own maintenance schedule, but effectively is the same as if the user were to do it within the SSMS). You may need to change which user performs that task.
-You may need to re-do the backup schedules (which I assume you already have but should mention it)
-If you ar
Read More...

I can confirm an email did go out, as I received it. But I'm also on about 20 client accounts under Blackbaud.com, so there could be all sorts of criteria I made it in under
Read More...

Yes, sorry about that. I was thinking Financial Edge for some reason. RE allows it, FE/EE do not.
Read More...

Deleting old users:
-Name is unique, so if a jsmith is deleted and you use jsmith again, you will not be able to add them
-User remains on the USERS table on the backend with a value in the DELETED column of -1. WARNING I DO NOT CONDONE THE NEXT PART OF THIS SENTENCE AS THIS MADE INVALIDATE AGREEMENT WITH BLACKBAUD BUT I MERELY MENTION IT AS A THEORETICAL... If you have access to SQL you can change this to "0" and the person will reappear, and in all lists.

Querying on old users:
-You can
Read More...