Re: Converting from an ancient BASIC to new database

DAVID <david@[EMAIL PROTECTED]
> wrote:
> Overlays?
>
> VB classic requires that each module be small,
> and that there be no overlap between the modules.
>
> It can sometimes be very difficult to convert
> classic code with overlays to VB, because the
> only clean way to convert is as one big program,
> and then the big program is too large to compile.

Huh?  Examples, please?  At least some sort of description, of what
*possible* 
coding horror you're looking at where this was actually an issue?

> I would certainly give it a shot, but I already
> own a copy of VB6, (which is a discontinued product.)
>
> But if it is big, I would choose to use
> Powerbasic (already mentioned in this thread)

Also a very good product.  But the size of a DOS BASIC codebase never
seemed to be 
much of a deciding factor in this decision.  Also, other than hardware
specific 
methods, nearly all DOS MSBASIC code loads and runs directly in VB6. 
Granted, 
perhaps not a factor with "Thoroughbred Basic" but worth mentioning in any
VB/PB 
case.

(Why is this thread even in a *.dotnet.* group, anyway?)
-- 
..NET: It's About Trust!
 http://vfred.mvps.org