Hi John,

OK, I exaggerated a little, sorry. To the vulnerability issue I will rephrase an analogy that I gave to Bonnie:

Let's say you have a nice, old car which you are comfortable with, but everyone tell you that you must trade it in for a new, more modern car. You test a new car, and find that the locks are bad. Would you accept the comment from the salesman that since your old car has bad locks, you shouldn't worry? And if it bothers you, you can fix it easily? Wouldn't you expect the new car to be more secure than your old 'faithful' car?

I would expect my source to be safe by default in a new environment like .net, wouldn't you also?
>>>
>I see absolutely NO FUTURE FOR .NET !! Who wants to give away their source code?
>>>
>
>Are you making this determination based on a perceived weakness that EXE's can be de-compiled? There are .NET code obfuscators. Indeed, the situation right now is less than perfect - but it will get better. And as Bonnie said, Fox EXE's can also be de-compiled.
>
>All that said, it logically does not follow that because .NET EXE's can be decompiled - .NET has no future. If that is so, then you would have to say that VFP has no future either.