-=> Quoting Alan Morrison to Abb Naklie <=-
 -=> Quoting Abb Naklie to David Powell <=-
 Hi Alan,
 AM> It is also very new to me as I've been an old xbase programmer from
 AM> FoxBase 1.0 days.  It appears 5.0 can only build 32 bit code, requiring
 AM> all my installed customer base to get rid of their old windows 3.1
 AM> systems.  Am I correct on this?
 Yup, it's all 32 bit. M$ is hell bent on killing Windows 16 bit. However,
 many companies aren't switching to Win 32 bit. As they say, if it ain't
 broke, why fix it? And fixing something that ain't broke wastes money.
 The main company I deal with hasn't switched to Windows 95 yet. It has
 no _need_ to yet. All the dos and Windows 3.1 based programs they use
 (and I've done for them) satisfy their _needs_. I agree with Den and
 David here that there is a big market out there for a 16 bit version
 of Visual FoxPro, or a new 16 bit FoxPro of some kind. However, on
 the other side of the coin, you can do a lot with 32 bit apps that
 ya can't with 16. I personally prefer to move forward - I wouldn't
 want to go back to the days of the Commodore VIC-20....:)
 AM> Also appears the support files make the distribution HUGE!  I did a
 AM> convert on an existing APP that was 1.8 meg which grew to 3.5 meg in
 AM> 5.0!  I assume I can find ways to improve on this, but some hints at
 AM> such things on the echo would be appreciated!
 I've noticed it too, and not just with VFP 5 but with Delphi and now
 Access 97. The 32 bit application counter parts _are_ larger, but
 nicer. Have fun, and don't be afraid to swear a lot (or "whine" )!
 Take Care
 Abb
... Anyone who clings to dying technology is being left behind...
---
   Blue Wave/DOS v2.30 [NR]  
 - JetMail v1.20 6 - Unregistered QWK Mail Door for Spitfire
--- SFScan v2.00
---------------