Carl,

Any mention at all of a VFP-to-VFP capability *WITHOUT* need for ODBC???

Any mention of improvements to Help, and documentation generally???

Any mention of something better than the KnowledgeBase for communicating known problems and fixes???

All in all, sounds exciting, but some of the more drab stuff is imporatant too.

Cheers,
Jim N

>Here's what I could get out of the Monday night session preview of
>the upcoming VFP6, code named Tahoe:
>
>Full support for Microsoft Transaction Server (MTS)
> o VFP single threading changed to apartment model threading
> o MTS will manage multiple instances of VFP6 for you
> o allows VFP to fully participate in Visual Studio as a tool
> that can be used for building true scalable components
>Active Documents
> o Scrollbar property (None, Horizontal, Vertical, Both) so
> VFP6 will reflect behavior shown in Internet Explorer (IE)
> o OLEDragAndDrop Property
>And More...
> o INDEXSEEK function which allows you to find a key value within
> an index *without* moving the record pointer
> o AGETCLASS and AVCXCLASSES to obtain class info without
> opening the class
> o all of the file functions normally contained in FOXTOOLS.FLL
> are now native to the VFP language
> o NEWOBJECT function
> o _INCLUDE=
> o hyperlink component for forms (as seen in Office 97 Access)
> o GIF file support with preview capability when picking file
> o VARTYPE function to use with objects
> o capability to compare form name with _screen
> o every base class has AddProperty
> o TRANSFORM function will take any data type and automatically
> convert it to a string (i.e., no DTOC needed for {09/15/97})
> o STRTOFILE function (instead of FOPEN)
> o FILETOSTR function
> o and much, much more.
>
>Also, it was regretfully comunicated to us that there are no current plans
>for a new updated Mac version of VFP. The cross-platform stuff is intended
>to be handled via Internet Explorer on the Mac and UNIX.