Mick_Webb
New Member
- Joined
- Apr 4, 2016
- Messages
- 17
- Office Version
- 2016
- 2013
- 2010
- 2007
- Platform
- Windows
Does anyone else share my frustration with the following? Or better still has found a solution?
I am using Office 2016 on a Windows 10 64 bit OS.
I cannot get the FileDialog.InitialView Property to take effect - i.e. no matter which of the msoFileDialogView constants I use it is not applied in the dialog when it opens.
It accepts a valid constant value - an invalid one produces an error - and you can read it after writing it, in fact it will still have this value on a sequential run of the dialog, but it does nothing with it.
Different folders come up with different views - I thought it was a reflection of the view set in File Explorer but a folder will come up on the dialog with a different view from File Explorer. I even, programmatically, changed all folders to be of the General type template to no avail.
If I change the view on a folder manually on the dialog it will come up with this on sequential runs - the read value of the FileDialog.InitialView Property being whatever it was set to in the code on the previous run.
I also have Office 2010 on the machine and this comes up the same, so do suspect it is a Windows 10 thing.
Any thoughts appreciated.
I am using Office 2016 on a Windows 10 64 bit OS.
I cannot get the FileDialog.InitialView Property to take effect - i.e. no matter which of the msoFileDialogView constants I use it is not applied in the dialog when it opens.
It accepts a valid constant value - an invalid one produces an error - and you can read it after writing it, in fact it will still have this value on a sequential run of the dialog, but it does nothing with it.
Different folders come up with different views - I thought it was a reflection of the view set in File Explorer but a folder will come up on the dialog with a different view from File Explorer. I even, programmatically, changed all folders to be of the General type template to no avail.
If I change the view on a folder manually on the dialog it will come up with this on sequential runs - the read value of the FileDialog.InitialView Property being whatever it was set to in the code on the previous run.
I also have Office 2010 on the machine and this comes up the same, so do suspect it is a Windows 10 thing.
Any thoughts appreciated.
