This was actually done 'by design'...
![Wink [;)]](/emoticons/emotion-5.gif)
You are, of course, correct that this has been a source of confusion for a number of users and therefore it is clearly a defficiency of the logic behind our future-date handling.
Here's an interesting point to consider: imagine you run a report without date restrictions, but you only expect 'active' data to be displayed. Now, run the same report but this time restrict the date range - including providing a time in the past, but BEFORE the effective date of this future-dated record. You wouldn't expect to see it, right? Now change the report again, so that it ENDS today - before the 'start date' of the record: you'd still not expect to see the record.
The point I'm trying to make is that in some circumstances it may actually be 'reasonable' for HealthFrame to treat future-dated records the way we currently do - and other times it isn't so obvious what's going on.
We'll pass the concern to our development team.
Thanks!
Support Team