Re: p-code
- From: "MikeD" <nobody@xxxxxxxxxxx>
- Date: Thu, 17 Aug 2006 16:50:19 -0400
"Stephen Howe" <stephenPOINThoweATtns-globalPOINTcom> wrote in message news:%23KXDBtjwGHA.4280@xxxxxxxxxxxxxxxxxxxxxxx
And just because you say that we're supposed to believe you? <vbg>
No I guess not. But the fact that it is off the beaten track, a 10-year old
product, 16-bit rather than the current generation might make you think
otherwise.
Situation is that I have the previous source code to an executable, but not
the current source to the current executable.
They differ by 7K. A 3rd party company was used to do Y2K work in late 1999
(make sure 2-digit years dont cause a problem). For whatever reason (I was
not involved in this), we did not get the modified source. 3rd party
company has vanished. This executable is supposed to be "retired" but
customers are still using it. And now we need to fix a few things. So I am
hoping to overcome the 7K gap. Not impossible.
I seriously doubt you'll be able to recover the source code in any kind of meaningful or useful form. I believe your probably stuck with working from the source code you have for the older version and just redoing whatever was changed between it and the later version. Hopefully, you do know what features got added or bugs that got fixed.
--
Mike
Microsoft MVP Visual Basic
.
- Follow-Ups:
- Re: p-code
- From: Stephen Howe
- Re: p-code
- References:
- p-code
- From: Stephen Howe
- Re: p-code
- From: MikeD
- Re: p-code
- From: Stephen Howe
- p-code
- Prev by Date: Re: Restarting the app
- Next by Date: Re: vb and msxml - encoding conversion is not working
- Previous by thread: Re: p-code
- Next by thread: Re: p-code
- Index(es):
Relevant Pages
|