Re: p-code
- From: "Stephen Howe" <stephenPOINThoweATtns-globalPOINTcom>
- Date: Thu, 17 Aug 2006 21:25:14 +0100
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.
Stephen Howe
.
- Follow-Ups:
- Re: p-code
- From: Bob O`Bob
- Re: p-code
- From: MikeD
- Re: p-code
- References:
- p-code
- From: Stephen Howe
- Re: p-code
- From: MikeD
- p-code
- Prev by Date: Re: Downgrade from .net to VB6 (here few ppl have .NET FW 2.0)
- Next by Date: Attaching keyboard shortcut to command button in graphical style
- Previous by thread: Re: p-code
- Next by thread: Re: p-code
- Index(es):
Loading