Old VBA Code No Longer Working

[Joe4]

Last year, I wrote some VBA code for another department. One of the steps was to import a bunch of files based on their file prefix (most of the files have date stamps built into their names).

An example of one of those sections looks like this:

'   Open data file
    Dim dFile As String
    dFile = "C:\Temp\Macros\Data\Assets - All*.xlsx"
    Workbooks.Open Filename:=dFile

(note that there will always be exactly one file in this folder with the "Assets - All" prefix.

It ran fine, and the department has been using it for the last year. Now, they have some adjustments to make to the code.
Now, when I try to run it, I am getting this error message.

I confirmed that there exactly one file in this folder with this prefix (and file extension), and it is not currently open.
If I rename it to "C:\Temp\Macros\Data\Assets - All.xlsx" and then update the line of VBA code to say:

    dFile = "C:\Temp\Macros\Data\Assets - All.xlsx"

if will successfully open the file.
So it appears that something changed where it no longer likes the wildcard in the file name (though it worked just fine in the past with that in there).

The only thing that changed since I worked on this last year was I recently got a new computer. Both ran Excel 365, but I upgraded from Windows 10 to Windows 11.
And yes, when you view the files in File Explorer, it does show the file extension.

Any ideas what may be going on and why this stop working?

Thanks

 

[Micron]

Lots of posts here and there saying you can't do it this way. It's my experience that application or Windows updates tend to make code that worked suddenly not work. The usual solution is to fix the code because it was never quite correct - people just got away with it until they didn't.

VBA: Wildcard not working with existing code

I have an interesting issue that you may be able to shed some light on. I have a macro in spreadsheet that opens a csv file that is in the same directory, manipulates it and saves it to another folder. The csv file file always has the same name and that name is hard-coded into the macro...

www.mrexcel.com

 

[Joe4]

Lots of posts here and there saying you can't do it this way. It's my experience that application or Windows updates tend to make code that worked suddenly not work. The usual solution is to fix the code because it was never quite correct - people just got away with it until they didn't.

VBA: Wildcard not working with existing code

I have an interesting issue that you may be able to shed some light on. I have a macro in spreadsheet that opens a csv file that is in the same directory, manipulates it and saves it to another folder. The csv file file always has the same name and that name is hard-coded into the macro...

www.mrexcel.com

Thanks, that fixed it!

To be honest, I was a little surprised that the original code worked in the first place...

 

[Micron]

Glad I could point you in the right direction & thanks for the recognition.
I've seen several issues posted in AccessForums.net about old code no longer working and every one of them was malformed code that they somehow got away with for a time. The usual trigger was that the application had been updated, plus it seemed that M$ introduced a new bug every time there was an update. It's why I turned updates off for Office apps.