In my 32 bit Application, When I use the Terminal Emulator, it uses the Windows Explorer type Dialog Boxes when you Open or Save a File. If I use the File Transfer routines directly in my program (without the Terminal Emulator), they too, allow for Long File Names and use the Explorer type Dialog Box. However, when I use the Clarion FileDialog() Procedure, it uses the old 16 Bit File Open and Save Dialog Boxes, and they just don't fit in with my 32 bit program. How is CLACom able to use the Explorer type Dialog Boxes and Clarion can't? I really need to be able to utilize Long File Names in my program.

Clarion needs to maintain compatibility with 16 bit programs. Because of this compatibility issue, 32 bit programs are "stuck" with a 16 bit interface unless you directly call the 32 bit WIN API functions.

CLACom provides Templates and Functions that you can use in your Application to utilize Long File Names and the Explorer type File Open/Save Dialog Boxes. There is a Template procedure called GetOpenSaveFile() that will allow you to prompt a user for a file to Open or Save As. There is also a Control that you can use on your Windows that provides the standard "ellipses" button. If a user clicks on the button, the Enhanced Explorer type File Open Dialog Box appears instead of the dreaded 16 bit Dialog Box.

Note that starting with Version 4 of Clarion, the FileDialog() Procedure allows for Long filenames and Enhanced Explorer type Dialog Boxes. If you haven't yet upgraded to Clarion 4 or 5, you might want to consider doing so.