> Then, when you're told to upgrade you discover that the
> app won't run on the new machine, the developer that
> created it and understood it left 2 years ago, ...
Been there at the front end, documented that, backed it
all up, labeled the media, and they never had to call.
> ... and you are not quite sure where the latest
> version of the source code is.
Hmmm. I thought that one of the main reasons for using
an interpreted or run-time-compiled language like BASIC
was that the source WAS the executable ...
... or are you now going to tell me that MS VB can be
fully compiled to binary files that can get separated
from the source, and the source lost?
>>Hmmm. I thought that one of the main reasons for using
an interpreted or run-time-compiled language like BASIC
was that the source WAS the executable ... <<
Only the very earliest versions of Basic worked like that. I am pretty sure all versions of VB have seperate source and executable. If you lose the source, you are in trouble.