Bill Meyer

Nice! A little pricey!

https://www.clickykeyboards.com Has new and restored IBM keyboards from 25-30 years ago.

Alternately, you might recognize that the use case you cited is not supported.

You put your cursor in the TMyObject class, and then use Ctrl + Alt + M.

The 5900X is probably overkill, too. Mine is a 3800X and I've been running it for over a year. Glad I bought it. Would have liked to get a 12 core, but in truth, my experience has been that the 8 core is a very good fit. You could get a 3900X and use the $200+ toward memory. In my environment, 64GB is now the sweet spot.

I am very happy with my AMD in a system where it is not unusual to have multiple VMs running.

Understood. My recollection is that the misbehavior observed here was inconsistent. Sorry I don't have better details. What I do know is that after the fix was applied to the manifest, the system behaved as expected. Worth a try, I think.

I was not involved, but I know we had some issues which were resolved by the info here: https://stackoverflow.com/questions/23551112/how-can-i-set-the-dpiaware-property-in-a-windows-application-manifest-to-per-mo#44009779

Dataset.Filter and Dataset.Filtered? Or are you looking for more than that?

One of the first things I override. 😉

Yes. The extension was incorrect at the call, and they silently correct it. I'd have preferred an error message.

And obviously going blind. Thank you! But that's really odd, as the content of my filename variable has not changed.

Here is a selection from the Process Monitor log which shows the last few entries of the file write activity, and the subsequent failure to find the file: "Time of Day","Process Name","PID","Operation","Path","Result","Detail" "5:54:48.3007155 AM","MediaOffice.exe","7476","WriteFile","T:\TestSheet.xlsx","SUCCESS","Offset: 17,179, Length: 46" "5:54:48.3007203 AM","MediaOffice.exe","7476","WriteFile","T:\TestSheet.xlsx","SUCCESS","Offset: 17,225, Length: 19" "5:54:48.3007257 AM","MediaOffice.exe","7476","WriteFile","T:\TestSheet.xlsx","SUCCESS","Offset: 17,244, Length: 22" "5:54:48.3010912 AM","MediaOffice.exe","7476","CloseFile","T:\TestSheet.xlsx","SUCCESS","" "5:54:48.3363273 AM","MediaOffice.exe","7476","QueryOpen","T:\TestSheet.xls","NAME NOT FOUND","" "5:54:48.3363673 AM","MediaOffice.exe","7476","QueryOpen","T:\TestSheet.xls","NAME NOT FOUND","" "5:54:48.3363977 AM","MediaOffice.exe","7476","CreateFile","T:\TestSheet.xls","NAME NOT FOUND","Desired Access: Write Attributes, Synchronize, Disposition: Open, Options: Synchronous IO Non-Alert, Open Reparse Point, Attributes: n/a, ShareMode: Read, Write, Delete, AllocationSize: n/a" "5:54:48.3364372 AM","MediaOffice.exe","7476","QueryOpen","T:\TestSheet.xls","NAME NOT FOUND","" And here, a sample of the activity which appears to be from the FileExists() call: "Time of Day","Process Name","PID","Operation","Path","Result","Detail" "5:54:48.3639990 AM","MediaOffice.exe","7476","CloseFile","C:\Windows\Fonts\segoeuib.ttf","SUCCESS","" "5:54:48.3640382 AM","MediaOffice.exe","7476","CloseFile","C:\Windows\Fonts\segoeuii.ttf","SUCCESS","" "5:54:48.3640635 AM","MediaOffice.exe","7476","CloseFile","C:\Windows\Fonts\segoeuiz.ttf","SUCCESS","" "5:54:48.3645094 AM","MediaOffice.exe","7476","QueryOpen","T:\TestSheet.xls","NAME NOT FOUND","" "5:54:48.3645566 AM","MediaOffice.exe","7476","QueryOpen","T:\TestSheet.xls","NAME NOT FOUND","" "5:54:48.3645860 AM","MediaOffice.exe","7476","QueryOpen","T:\TestSheet.xls","NAME NOT FOUND","" "5:54:48.3646129 AM","MediaOffice.exe","7476","QueryOpen","T:\TestSheet.xls","NAME NOT FOUND","" These entries continue for many hundreds of rows. I am not accustomed to investigating at this level, so not sure how to interpret this.

But as I wrote above, the file clearly does exist.

This app created the file. A few lines later, it looks for the file, and GetLastError reports 2: ERROR_FILE_NOT_FOUND But the file exists, in that same location. It is openable in Excel, and can be resaved from Excel. And after that, I still get a fail on FileExists().