Sign Up

Sign Up to our social questions and Answers Engine to ask questions, answer people’s questions, and connect with other people.

Have an account? Sign In

Have an account? Sign In Now

Sign In

Login to our social questions & Answers Engine to ask questions answer people’s questions & connect with other people.

Sign Up Here

Forgot Password?

Don't have account, Sign Up Here

Forgot Password

Lost your password? Please enter your email address. You will receive a link and will create a new password via email.

Have an account? Sign In Now

You must login to ask a question.

Forgot Password?

Need An Account, Sign Up Here

Please briefly explain why you feel this question should be reported.

Please briefly explain why you feel this answer should be reported.

Please briefly explain why you feel this user should be reported.

Sign InSign Up

The Archive Base

The Archive Base Logo The Archive Base Logo

The Archive Base Navigation

  • SEARCH
  • Home
  • About Us
  • Blog
  • Contact Us
Search
Ask A Question

Mobile menu

Close
Ask a Question
  • Home
  • Add group
  • Groups page
  • Feed
  • User Profile
  • Communities
  • Questions
    • New Questions
    • Trending Questions
    • Must read Questions
    • Hot Questions
  • Polls
  • Tags
  • Badges
  • Buy Points
  • Users
  • Help
  • Buy Theme
  • SEARCH
Home/ Questions/Q 6120991
In Process

The Archive Base Latest Questions

Editorial Team
  • 0
Editorial Team
Asked: May 23, 20262026-05-23T15:43:58+00:00 2026-05-23T15:43:58+00:00

I have a VB6 application that does a directory listing of a folder and

  • 0

I have a VB6 application that does a directory listing of a folder and picks up the filenames. Some of these are accented, for example “Guimarães.txt” (small A with a tilde). Both the VB Dir function, and FileSystemObject functions are unable to recognise the accented character, and instead return the filename as “Guimar?es.pdf”, so I am subsequently unable to open the file. I can see the file correctly in Windows Explorer

This is only happening in one live environment, running Windows Server 2003 R2. On our test systems, we can read the file correctly, though these are mainly Windows 2008 and Windows 7. I initially thought it was down to the version of FSO, but as “Dir” gives the same results, I no longer think so. Also, when I write the name of the file to a log file, it is also incorrect. So I think that at a very early stage it is unable to handle the character, and replaces it with a question mark.

What I need to establish is the cause of the issue: is it down to the version of Windows, or my regional settings (which I am unable to view, as my account is locked down), and what can I do to resolve the problem. For now, I’ve asked the users not to use these characters, but this is not a long-term solution.

Thanks.

  • 1 1 Answer
  • 0 Views
  • 0 Followers
  • 0
Share
  • Facebook
  • Report

Leave an answer
Cancel reply

You must login to add an answer.

Forgot Password?

Need An Account, Sign Up Here

1 Answer

  • Voted
  • Oldest
  • Recent
  • Random
  1. Editorial Team
    Editorial Team
    2026-05-23T15:43:59+00:00Added an answer on May 23, 2026 at 3:43 pm

    Ok, the file name being read off disk uses unicode.
    When you try and display this, the font in use doesn’t support that glyph so it shows the “?”, but writing it to disk writes the correct representation.
    When this is then passed to the file functions, it’s “converted” to MBCS or another charset which then breask.

    You can either change your code to use the native wide Win32 API calls, or just change the “langauge for non unicode programs” to match the language used in the filename.

    • 0
    • Reply
    • Share
      Share
      • Share on Facebook
      • Share on Twitter
      • Share on LinkedIn
      • Share on WhatsApp
      • Report

Sidebar

Related Questions

I have some old code (an old but still maintained VB6 application) that from
I have a VB6 application that still references some old VB5 libraries (dll, vbr,
I have a VB6 application that needs to update it's self. For this purpose,
I have a legacy VB6 application that was built using MSDE. As many client's
I have a legacy VB6 application that uploads file attachments to a database BLOB
I have a VB6 desktop application that is deployed on well over 1200 desktops.
I have a VB6's Application that is in production environment right now, this application
I have inherited a VB6/Access application that we have developed and sold for many
I have VB6 application , I want to put some good error handling finction
I have a legacy VB6 application that has the following structure defined: Public Type

Explore

  • Home
  • Add group
  • Groups page
  • Communities
  • Questions
    • New Questions
    • Trending Questions
    • Must read Questions
    • Hot Questions
  • Polls
  • Tags
  • Badges
  • Users
  • Help
  • SEARCH

Footer

© 2021 The Archive Base. All Rights Reserved
With Love by The Archive Base

Insert/edit link

Enter the destination URL

Or link to existing content

    No search term specified. Showing recent items. Search or use up and down arrow keys to select an item.