>Bernard -
>
>Could you expand on what you mean and what classes are not updated correctly?
>
>See Lisa's post about it here:
>http://spacefold.com/lisa/post/SP2-Sedna-FFC-ReportListener-Beta-Info.aspx
>
>There are two issues. It looks like MSFT have addressed the second one for the final, released SP2 patch.
>
>1) If you've opened or browsed FFC class libraries using the MODIFY CLASS ? dialog then this is an issue - the file date stamp gets touched and the patch thinks you have changed the files and may only replace the VCX file, leaving the VCT file out of sync (for example).
>
>2) The SP1 patch updates numerous files. During beta, the SP2 patch mistakenly thought that some of the SP1-touched files were "user modified" and did not patch them, leaving the files in the FFC directory a mixture of different versions. Subsequently recompiling these files caused errors. THIS APPEARS TO BE FIXED NOW.
>
>However, issue #1 is still a problem. So long as MODIFY CLASS ? can touch the VCT file date and time, the potential for the patch to skip some files is still there.
>
>So to be 100% sure, I still recommend patching a clean RTM install with the SP2 patch.
>
>- Colin
Thanks Colin. Youve explained it to me. I will have to recheck the dates in the FFC. I am sure that very few people know about this potential problem. Thanks for pointing it out.

Is there a way to split the .MSP from the setup and extract ALL the FFC files?