Long File Name problems in 16-bit VB4 on Win95
If you don't mind a little extra overhead, you can write the conversion
functions in a 32-bit OLE EXE server and create an instance of the class in
your 16-bit application. The 32-bit server should have functions to
convert filenames. However, this way is wrought with slow performance, as
not only are process boundaries crossed, but OLE compatibility systems,
too.
- James
Quote:
> Long filenames are unavailable in 16 bit windows, or from 16 bit VB under
> Win95. You'll have to recompile using VB4-32 or VB5.
> --
> Randy Birch, MVP Visual Basic
> Moderator, Fidonet Visual Basic Programmer's Conference
> VBnet, The Visual Basic Developers Resource Centre
> http://home.sprynet.com/sprynet/rasanen/
> : We have an app developed in VB4 for 16-bit on WIndows 95 that is being
> : used under Win95. Now the user wants to read long file name graphics
> : from the Application. The problems I am seeing are when I use the
> : FileLen function to check if file exists, it returns error if file name
> : passed is longer than 8 characters. Also, the third party control has
> : problem opening this file.
> :
> : So, I want to convert the files longer than 8 characters to the DOS
name
> : (with tilda). When I use the Win API call for 32-bit (kernel 32), I get
> : invalid DLL error.
> :
> : I would like to know how I can make VB FileLen function to work
> : properly in my App and also how to use the Win32 API call in this
> : version.
> :
> : I should appreciate any feedback on this.
> :
> : Krishna
> :
> :