Hi all,
I'm looking for some advice about the start date parameter for the Membership Update Report. We have our report scheduled to run once a month at the beginning of the month. So, this month, the report ran on 2/2/10 with a start date of 1/2/10 and an end date of 2/2/10.
The problem we are having is this: if a member renews late, the membership update report is not picking them up and moving them to current. We had a member with an initiation date in October who renewed in January. The February run of the report did not update her record.
In our TEST system, I was able to fix this issue by widening the date range to an entire year. Even though it didn't appear to create any problems in TEST, I'm hesitant to take this step in LIVE without some further input.
Has anyone run into an issue like this?
Does anyone run their Membership Update Report monthly with a year-long date range?
I look forward to hearing your thoughts!
Mara,
I should have mentioned that like Beth our start date in the past is 1/1/2004. By doing this we do not have any issues with missed late renewals. Also I should mention that the documentation for the Member Update Report warns against setting the END DATE in the future as Dale says he does by using RunDate+2. I think just setting your START DATE in the past will solve your problem. Just like you did when you fixed it.
Normal 0 false false false EN-US X-NONE X-NONE MicrosoftInternetExplorer4
NOTE: The End Date parameter should generally not be set to date in the future, as doing so could update membership records prematurely.
Thanks, everyone, for all of your replies!! I am going to take your advice, and I feel much more confident about it now!
Thanks again!