>Noone suggested that previous versions of the tool stopped working. In fact I am still using it (2.9.2a) to produce UML for our future endeavors. I think of it like this. Would you remain a VFP coder if the next version of VFP did not support any of the previous code you wrote? What if VFP dropped a major feature such as its native data engine and advertised that in its place you would have MSDE only?
>
>Bottom line is I am too satisfied with VUML 2.9.2 to be presented with it lacking support for CC Rider and VFP going forward.

Good points. Especially from a VFP point of view.

It is also worth noting that the world's biggest developer community (that would be Visual Basic) goes through exactly the scenario you describe with pretty much every version. No data compatibility. Often no language compatibility... ;-)

Markus