Marc, Is it possible to get an ERD so that table joins/relationships in MSSQL would be visible to us?  It's difficult to report accurately when you cannot be certain of the relationships, especially when primary/foreign keys do not share the same name.

Does anyone have an autorenew program in place that wouldn't mind discussing it? Obviously, PE just has a checkbox with no functionality, no reporting, etc.  We would like to set up an auto renewal program and wanted to see how others were implementing it around the limitations of PE.  Call, email, post, whatever works for ...

Changing my question a bit - do any of you have PE and RE with separate donor and member programs, where both are sold out of RE?  If so, we'd love to talk to you about your processes, reporting, etc. vickiy@childrensmuseum.org 317-334-3210

Do any of you have 2 membership programs?  We use PE and RE and are considering selling memberships out of RE instead of PE.  We would love to talk to other organizations doing this.  We're interested in processes and reporting, mostly. Please contact me if you're willing to discuss your membership management ...

Hi, We're a very large organization with a long RE history, and we've had PE about 3 years now.  Donor memberships are housed in RE, Member memberships are sold from PE.  Even before PE, these were separate because processing occurs in 2 different depts. There is discussion about selling 'member' memberships out of RE ...

No experience, just something to try - try different font barcodes. 

PEO should allow an existing member to upgrade their membership while they can currently only renew at the same level.  they want $20k from us to do this, which would be a customization, which is not guaranteed to work in any version but the one we're on.

Sounds great, but, since they've cut server money for the next 3 years, we can't do anything.   So many times when I update an app I have to bounce the server - wouldn't same still be true, but affect well more than its own app space?  

We're a large non-profit, one app per server, and used to be on a 3-year replacement schedule.  With the economic downturn, they're wanting to stretch them for 6 years.   What has been your policy; has it changed due to the economy?  Not being a hardware person, what do you consider Best Practice?  thanks

We did try that, but no go.  They are now telling us that the next release, end of quarter, will fix the problem.  Thanks for your input!