Community
Some customization files (such as AutoLISP routines) may set FILEDIA to 0 so that when they perform a file-related action (such as save), the dialog box does not display and interrupt the flow of the program. Good practice would have the routine reset the value to its original value after the file-related action is complete. Really good practice would include an error handling system that, if the routine crashes, would reset any changed system variables. (I confess that most of my routines do not have error handling, but they do reset the variables.)
If you use a routine that does not reset variables, or crash out of one before the FILEDIA variable was reset (and there is no error handling), FILEDIA could end up getting changed to 0 without you realizing it.
That is certainly strange. If the issue is that the file-related dialog boxes are opening off-screen, you might try pressing ALT+SPACE BAR, then M and finally any arrow key. That should bring the dialog to the cursor, and you can then move it where you want and left click to place it. If it is something else, that may not help.
One thought: on that computer, does the user have write authority to the folder where the main customization file is stored? If resetting brings the file dialogs back, but closing the program and reopening program loses them again, then that suggest to me that the reset locations for the dialogs is not being saved on exit, and is then reverting to the old, off-screen location(s).
The position of out-of-the-box palettes and dialogs is, so far as I know, "remembered" in the main CUIX file. There may be something in the registry, too, but I am not certain about that. If the person with the issue cannot overwrite the main CUIX file (which would not be a good idea for any user, unless you really, REALLY want to lock down the interface), then, after resetting the location to using ALT+SPACE BAR, M, ARROW KEY to get it working temporarily, there may be an event that triggers a reload from a source that still has the dialog off-screen. I have never had that much trouble, so I have never had this problem. Our main CUIX file is in the user's roaming Microsoft/AutoCAD profile on their local hard drive. If someone mucks the file up badly, we have a copy we can use to overwrite it. If that causes personal settings to be lost, I will repeat the littany of putting all personal interface customizations in a custom, partial CUIX file, and that they back that file up early and often.
I do not mind if others want to customize their workspaces in AutoCAD (I used to, when I was an architect out on the floor), but if those get lost, my policy is that is on them. Most people clever enough to customize the interface understand that; those who do not rarely argue the point.
@s.deslandes wrote:
That solved it for as well but what is intriguing to me is how that got changed...??????
Assuming that you have solved it by setting FILEDIA to 1, see this post in this thread (message #8 at the time I am writing this) for one way that FILEDIA can get set to 0 without directly doing so.
![Autodesk Design & Make Report](https://forums.autodesk.com/t5/image/serverpage/image-id/1350519iCB55845EBFC43016/image-size/large?v=v2&px=999" "Autodesk Design & Make Report")
