× The internal search function is temporarily non-functional. The current search engine is no longer viable and we are researching alternatives.
As a stop gap measure, we are using Google's custom search engine service.
If you know of an easy to use, open source, search engine ... please contact support@midrange.com.



Joe,

> how many RPG programs needed to change?
> 
> The answer of course is none, which was my point.

And as others pointed out, even the CL should not have needed to be
changed if the machine was configured properly.  If Longhorn ships
without the VB6 runtime DLLs pre-installed, this is like putting a VB6
executable on the machine then getting an error and assuming it must
be re-written in VB.NET instead of just installing the VB6 runtime
support.

That of course presumes the VB6 runtime DLLs will in fact install and
work correctly with Longhorn, and I don't know if that is guaranteed
to be true as of now.  However, my guess is that MS will bow to
pressure and attempt to make the runtime work, but be less concerned
if the VB6 IDE and compiler does not.  If so, you'd need to use a
dual-boot or alternative PC with older OS in order to create the
*.exe.  But even that remains to be seen.  I don't think even MS would
intentionally cripple VB6 though ("Longhorn isn't done until VB6 won't
run" ??).

I agree with most of your points, but do think you are over-stating
incompatibilities with programs designed for earlier versions of
Windows.  I have numerous things I wrote in 16-bit versions of VB3/4
or Access 2.0 under Windows 3.1 which are still in production use on
everything from Win95 to XP Pro SP2, because there hasn't been
justification to rewrite them since they still work.

Doug


As an Amazon Associate we earn from qualifying purchases.

This thread ...

Follow-Ups:
Replies:

Follow On AppleNews
Return to Archive home page | Return to MIDRANGE.COM home page

This mailing list archive is Copyright 1997-2024 by midrange.com and David Gibbs as a compilation work. Use of the archive is restricted to research of a business or technical nature. Any other uses are prohibited. Full details are available on our policy page. If you have questions about this, please contact [javascript protected email address].

Operating expenses for this site are earned using the Amazon Associate program and Google Adsense.