VB ->Thanks for the info. I thought it would be necessary to change the
   ->interface. I'm not happy at that, but if that's nearly the only thing to 
be
   ->changed, it's good news.
My thoughts exactly. Supposedly it'll let you have a mix of GUI and DOS
screens in the same program to aid in migration.
VB ->1) If I want to make 16 bit Windows 3.1 type executables -and-
Windows 95    ->ones, do I need either FiveWin or Clip4Win for the
first ones and XBase++    ->for the second? Or will just XBase++ do?
Clip-4-Win and FiveWin currently only produce 16 bit applications.
Xbase++ only produces 32 bit executables. The folks from FiveWin have
announced their own initiative for 32 bit programs, and from some of
John Skelton's comments, I think he's trying to port his code to
Xbase++. If that's the case, you could probably go with Clip-4-Win and
wait for his Xbase++ version. But of course you'd have to buy Xbase++
then.
In the US I think the 16 bit market is going to die off within a few
years. No one I know is doing any 16 bit development. It's because the
folks who have money are buying computers with Windows 95 and NT, and
the folks without money aren't. Which do you want for your customers?

VB ->2) Have you tried XBase++? I'd like to hear about your experience with 
it,
   ->if you have.
I installed the demo, but haven't really tried it yet. I did read the
help file documentation, and that's pretty good. Roger Donnay, a Clippr
old-timer and well-known Clipper third party market developer and
author, is now using it. He said he got his programs rewritten in
Xbase++ in two weeks, which is farther than he got in a year with
Visual Objects.
FWIW,
Raymond Pesek
 * 1st 2.00 #2448 * Moderator - Clipper Echo
--- InterEcho 1.19
---------------