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.
I tried to add this to ideas but it wouldn't work.
If you are in the position of having full spouse records for most of your consittuents you need to be careful to add the same prospect classification to both records. Assuming you are soliciting them as a couple. There is no way to audit where one person in a couple has one prospect classification and the other got no classification or another classification. If they have no classification they keep coming up in new potential prospect queries I run and they are already a prospect with their spouse.
I've filed it as a suggestion today that the field be accessible in query and export but it is not yet a full KB solution. If this is also a problem for you please file a case with case central and hopefully we will all be linked to the same KB ID.
In the meantime, we are using the classification "Spouse of a Prospect."
Drew
I also have such a prospect classification but how do you audit that all of the spouses have that classification? You can't query to find those that are missing that classification.
I also have such a prospect classification but how do you audit that all of the spouses have that classification? You can't query to find those that are missing that classification.
This won't work for everyone, but I do what I always do when the RE interface won't allow me to pull specific data, I use a SQL query.
It's possible, but unwieldy, to do this without using SQL. You can add an attribute to every prospect record, then use the Spouse Attributes to see if this attribute exists. Then you'll probably want to delete the attribute.
Once you have everything cleaned up, you can use VBA -- if you have it -- to automatically add the appropriate classification to spouses of prospects.
Drew
__________________ J. Drew Allen
Children's Hospital of Philadelphia
Crystal Reports and SQL Server Consultant
It is better to live your destiny imperfectly than to live an imitation of somebody else's life with perfection.
This won't work for everyone, but I do what I always do when the RE interface won't allow me to pull specific data, I use a SQL query.
It's possible, but unwieldy, to do this without using SQL. You can add an attribute to every prospect record, then use the Spouse Attributes to see if this attribute exists. Then you'll probably want to delete the attribute.
Once you have everything cleaned up, you can use VBA -- if you have it -- to automatically add the appropriate classification to spouses of prospects.
Drew
Don't laugh...I am on MSDE and do not have access to the server to do any querying from the backend. We are updaing servers hopefully within the ne next 30-60 days so I will have SQL server 2005 and RE 7.82 (WOO HOO) but until then I am stuck using query and export.
I may try the temporary attribute thing if it comes down to it. We are just getting into using classification and I am the one doing the reporting so for now I can live with a few errors until I have time to do the attribute.
VBA...ha ha very funny. I'll never see VBA as long as I keep working at small local non-profits.
Query on/Export Spouse Prospect Classification 
Linear Mode
