none
Problems with comdlg32.ocx, Windows Vista and long file names/extension´s

    Question

  • Hi Guy´s,

     

    Hope som expert here can help mee. I´m stuck´ed and tired after many days without sleep ...

     

    My VB6 SP5 application use comdl32.ocx (ver. 6.0.84.18). I use long files names and extension for my app, ex.:

    "my super file.kp [template]". I therefore set the filter to *.kp [template]. It´ works fine with XP, but no files i shown i the dialog box with Vista ?? If I manualle type in *.kp alle the files is show´n, and also if manually typing *.kp [template] !!!.

     

    So if someone could confirm that there is´ an known problem with comdlg32.ocx and Vista I will be gratefull, and if anyone now af  work-around I´ll be "JUBIIII...".

     

    Regards, Thomas (Denmark)

    Thursday, August 16, 2007 11:46 AM

Answers

  •  

    Issues found with VS or .NET are posted at the Connect (http://connect.microsoft.com) site.  You have to apply for a particular program but otherwise it is free.  Vista is not an option there.  The only way I'm aware of to report Vista issues is through Support Services (http://www.microsoft.com/services/microsoftservices/srv_support.mspx#itp) but you might have to pay for that.  Sort of stupid that MS doesn't allow you to report issues against its OS in an easy way.  Might be to cut down on the # of issues that are reported.

     

    Nevertheless you could just post the issue against VS.NET and indicate that you've followed it back to the Win32 API.  MS can then figure out who to report it to.

     

    Michael Taylor - 8/20/07

    http://p3net.mvps.org

     

    Monday, August 20, 2007 1:02 PM

All replies

  • This is a bug in the Vista implementation of the dialog.  It might be by design however.  Report the issue to MS.

     

    The following code replicates the problem:

    Code Snippet

    OpenFileDialog dlg = new OpenFileDialog();

    dlg.Filter = "Text Files|*.txt|Files|*.kp [template]|All Files|*.*";

    dlg.ShowDialog();

     

     

    Notice I added a couple of additional filters to ensure that filtering was working and that it wasn't an initialization issue.

     

    Michael Taylor - 8/16/07

    http://p3net.mvps.org

     

    Thursday, August 16, 2007 12:33 PM
  • Thank´s Michael.

     

    I´ll hope a servicepack soon will solve the problem. Not so funny to re-code the application becaus of a MS bug.

     

    Regards, Thomas

    Monday, August 20, 2007 5:29 AM
  • Hi Michael,

     

    Can´t find anywhere where private´s can report bug´s in developer tools ? any idea?

     

    regards, Thomas

    Monday, August 20, 2007 5:45 AM
  •  

    Issues found with VS or .NET are posted at the Connect (http://connect.microsoft.com) site.  You have to apply for a particular program but otherwise it is free.  Vista is not an option there.  The only way I'm aware of to report Vista issues is through Support Services (http://www.microsoft.com/services/microsoftservices/srv_support.mspx#itp) but you might have to pay for that.  Sort of stupid that MS doesn't allow you to report issues against its OS in an easy way.  Might be to cut down on the # of issues that are reported.

     

    Nevertheless you could just post the issue against VS.NET and indicate that you've followed it back to the Win32 API.  MS can then figure out who to report it to.

     

    Michael Taylor - 8/20/07

    http://p3net.mvps.org

     

    Monday, August 20, 2007 1:02 PM