| Stefan [MSFT] 2004-07-31, 7:48 am |
| Hi Alan,
it is a good idea not to do this!
You would break the Microsoft support boundaries.
Modifying the posting will modify the last modified date. That is as
expected.
You could create a custom property and copy the last modified date there and
then implement a sort routine based on this custom property.
Cheers,
Stefan.
--
This posting is provided "AS IS" with no warranties, and confers no rights.
MCMS FAQ:
http://download.microsoft.com/downl...6a/MCMS+2002+-+(complete)+FAQ.htm
MCMS Blog: http://blogs.msdn.com/stefan_gossner/category/4983.aspx
MCMS Sample Code:
http://www.gotdotnet.com/community/...t+S
erver
MCMS Whitepapers and other docs:
http://blogs.msdn.com/stefan_gossne...2/07/41859.aspx
--------------------------------
"Alan Taylor" <alan_taylor@nospam.uk.ibm.com> wrote in message
news:4vmlg0h2lsei1srghbkr42sthe7bl2gv84@
4ax.com...
> Hi.
>
> While a better means of managing content about to expire is being
> resolved I've written some code that interates though all postings and
> adds three months to their expiry. The consequence of this is that
> all modified postings have the LastModifiedDate updates.
>
> The problem is that I use this property to order content in descending
> order, so that older content is at the bottom, and the most current is
> at the top. Once my code has been run the LastModifiedDate no longer
> has the meaning it once had.
>
> Is there any way around this? I'd rather not have to write some SQL
> and change the backend data.
>
> Any thoughts?
>
> Alan
|