Also an interesting approach!
But the overhead of creating a new historical revision just to get a new
revision date is a little bit high.
If there would be an API to sort against the revision date, then this would
be a nice workaround.
But as there is no such feature I think it is more convenient to just copy
the last modified date to a custom property - which (btw) will also create a
new revision but access to the information is easier after this.

Cheers,
Stefan.

--
This posting is provided "AS IS" with no warranties, and confers no rights.

MCMS FAQ:
http://download.microsoft.com/downl...>
MCMS+2002+-+(complete)+FAQ.htm
MCMS Blog: http://blogs.msdn.com/stefan_gossner/category/4983.aspx
MCMS Sample Code:
http://www.gotdotnet.com/community/...nagement+Server
MCMS Whitepapers and other docs:
http://blogs.msdn.com/stefan_gossne...2/07/41859.aspx
--------------------------------


"Angus Logan" <angus_logan@data3.com.au> wrote in message
news:OsrIhIudEHA.3380@TK2MSFTNGP12.phx.gbl...
> Hi Alan,
>
> What if you were to use the Publishing API to:
>
> 0) load all the postings that you wish to increase their expiry date
> 1) iterate through the postings
> 2) save a new version of the posting
> 3) update the expiry date
> 4) Approve the posting so it is published
>
> There won't be any changes to the content but it will be Versioned as
though
> there is; so then you could view the Revision History of the posting to
see
> when it was actually last updated and when the expiry date was extended.
>
> The only problem with this is it may bloat your Database as you are
> versioning postings without actually changing the content.
>
> Also you mentioned updating the Database directly - if you it will
instantly
> invalidate the Microsoft Support Agreements for MCMS (so when you run into
a
> problem it is highly unlikely you will get any support).
>
> Do you think this solution may meet your requirements?
> --
>  ________________________________________

>
> Angus Logan  (MCAD/MCDBA/MCP)
> Lead Software Developer
> Microsoft Application Solutions
> Data#3 Limited
> E angus_logan@data3.com.au
> BLOG www.anguslogan.com
>  ________________________________________

>
> "Alan Taylor" <alan_taylor@nospam.uk.ibm.com> wrote in message
>  news:4vmlg0h2lsei1srghbkr42sthe7bl2gv84@
4ax.com... 
>
>

[ Post a follow-up to this message ]