Do any of the problem files have the same filename (disregarding the path information) as file that was included in project from which the EXE/APP was built?
Included files are always present and the path will always be ignored (i.e. regardless of the path you specify the file read will be the file that was included in the project).

>Hello Naoto,
>
>Same file names in different folder. Name of the files are all short.
>
>Regards.
>
>>A stupid question -- do any of the problem files have the same filename (ignoring the path) as an image that's included in the project from which the EXE was built?
>>
>>Another weird question -- could there be a conflict between a long filename and short filename? Perhaps you can check with "DIR /X" at the command line in the folder(s) in question to view both the lnog and short filenames. A long, long time ago, I ran into this sort of problem on an old Novell fileserver on which the short filename generation was performed by simply truncating the long filename -- this resulted on occasional clashes between long and short filenames (this was later corrected on the fileserver by loading a patch to change the short filename generation to use method similar to what's used in Windows 9x).
>>
>>>Hello all,
>>>
>>>Windows 11 (In case there could be something related to my problem)
>>>
>>>I have a folder that contains 36 images. When I use the file explorer and double-click to see the images everything is fine. Meaning that I can see the right image maximized.
>>>
>>>In my application I have to show an image in a form. Random(36) will determine which image will be viewed in the form. In the folder each image has a number that will identify it.
>>>
>>>The weird thing is that for two images I don't see the right image.
>>>
>>>To add to the weird aspect, I have another folder also containing Images. Images that also have a number to identify it.
>>>
>>>When I define which image goes where I use the path of the first folder. For the cases of the wrong images being displayed it's like the wrong images were taken from the second folder.
>>>
>>>So for example, hoping to make this problem as clear as possible here are the images displayed in my form.
>>>
>>>The 2 wrong images are the third and 36th.
>>>
>>>
>>>Folder1\Image1.png
>>>Folder1\Image2.png
>>>Folder2\Image3.png (this makes no sense because the path that I specify is with folder1.)
>>>Folder1\Image4.png
>>>Folder1\Image5.png
>>>Folder1\Image6.png
>>>Folder1\Image7.png
>>>Folder1\Image8.png
>>>Folder1\Image9.png
>>>Folder1\Image10.png
>>>Folder1\Image11.png
>>>Folder1\Image12.png
>>>Folder1\Image13.png
>>>Folder1\Image14.png
>>>Folder1\Image15.png
>>>Folder1\Image16.png
>>>Folder1\Image17.png
>>>Folder1\Image18.png
>>>Folder1\Image19.png
>>>Folder1\Image20.png
>>>Folder1\Image21.png
>>>Folder1\Image22.png
>>>Folder1\Image23.png
>>>Folder1\Image24.png
>>>Folder1\Image25.png
>>>Folder1\Image2.png
>>>Folder1\Image26.png
>>>Folder1\Image27.png
>>>Folder1\Image28.png
>>>Folder1\Image29.png
>>>Folder1\Image30.png
>>>Folder1\Image31.png
>>>Folder1\Image32.png
>>>Folder1\Image33.png
>>>Folder1\Image34.png
>>>Folder1\Image35.png
>>>Folder2\Image36.png (this makes no sense because the path that I specify is with folder1.)
>>>
>>>Did you ever see something like that?