Welcome to our forums
Bill
Your code runs OK for me in for both 32 bits and 64 bits. I don't get a DOS box.
As a natural instinct I would not click on OK before exiting from editing the name of the new folder but it turns out that (for me) it makes no difference to the outcome.
As an afterthought I also tried creating a sub-folder in a protected folder and this also works OK but naturally you do get a number of prompts to confirm the elevated status.
Hopefully it would not crash if the access rights were denied but I have not tested this.
Even if I just hit <Enter>, the same thing happens; crash.
The DOS box in 64 was a surprise because I included WINAPP. I seem to remember that maybe this isn't necessary anymore. I'll try changing the Project to set the /WINDOWS command line option and see if that make it not show up.
Bill
FYI: If I try to create a folder in an OPEN dialog (opening a file, or saving a file), the software exits, no traceback. Just quits.
Are you creating a simple subfolder (i.e. the main folder has full access rights)?
Are you able to test on other operating systems (i.e. different versions of Windows 10 or Windows 8)?
All my testing is a second level (or greater) in a folder already created by a regular (non-admin) user. So not likely it is a permissions issue. Also, I have done this on local drives and mapped drives. Same result.
Also:
What used to work on the laptop no longer works on the laptop. The result is always the same (crash, FP stack fault).
Bill
Going back a few posts, if a folder is created but not reported back correctly then the key is to complete creating the folder before you exit the browse dialog.
When editing you get a volatile edit box. After typing in the name of the folder, exit this edit box by clicking elsewhere (e.g. on its icon). Then the new folder will be created before exiting the dialog (via the OK button) and there should be no synchronization issue.
Paul, did that, still crash with FP Stack Fault. 32-bit.
Does exactly what you describe in 64 bit. No crash.
The new DLL's for 9.0 are working for this particular problem! Many thanks to Paul and the entire SilverFrost team!
Bill