>And, by the way, I think scenarios like this plus tighter than ever $$$ situations all around are what will be the biggest impediments to the widespread adoption of .NET.

Good story. Of course the moral of the story is...

Re-writing to .Net to get exactally what you have now is a BAD idea!!!

I think we would all agree that there are three common major goals as you put our newer versions of applications:

1. Make it do more
2. Make it easier to use/maintain/update
3. Make it more efficient (faster, cheaper hardware, etc)

You want to accomplish the above three goals even if you AREN'T changing your development tool/platform. However, what if just changing the tool and the environment gave you almost 80% of the above.

Of course, there are lots of other goals that the platform may give you for free:

1. Security
2. Stability
3. Scalability

So, don't move to .Net for the 'heck of it' move to .Net for what it will do for you.

The fact that .Net and managed code will be 'the thing' for the next 10 years or so, just like first DOS, then Win32 each had their eras... is just a bonus.

***********************

I guess I could ask you, why did you move your apps from FoxPro 2.x to VFP? Once you did it, was it 'exactally the same'? Of course not, it was faster (32-bit), more maintainable due to OOP, there was better data integrity due to buffering the DBC and transactions, etc, etc...

BOb