Why can't I browse to a file?

[chris54]

My Autocad days are few and far between these days, so hopefully this is an easy question. 

From the Getting Started page, if I click "Open Files", I get a prompt in the command line to enter a file name.  If I enter (manually) a valid path to a file, it will open.  I would expect that clicking "Open Files" would take me to an explorer window where I can browse to my file(s).  And once I've clicked on Open Files, the rest of the program is "dormant", waiting on me to enter a file name.  EVERYTHING else is either dimmed or inactive at this point.

Any ideas on why I'm not able to browse to the file??

This Acade 2016 is part of Inventor Ulimate (or what ever they're calling this week).

Thanks!

Chris

[rhesusminus · Accepted solution]

Type FILEDIA on the command line, and set it to 1.
That should take care of it.

[dougmcalexander]

I have reported this to Autodesk, but I'm wondering if anyone else has had an issue with their FILEDIA setting changing by itself. I haven't ever had an issue withn this until release 2016.  Now I have to ocassionally set it back.  I've seen other people post about this in the past but have never had the issue myself until release 2016.  It has happened several times.  Just curious.

[Anonymous]

I have this happen at quite often with 2016 and as you mentioned nevr had this issue with previous versions. 

[dougmcalexander]

Hi Jim,

Autodesk has asked me to try to document what I was doing just prior to the FILEDIA changing.  It seems random to me, but if you happen to be able to catch it please advise.  It could be related to the AutoCAD side, not Electrical.  I haven't yet searched the AutoCAD Discussion Group to see if any Vanilla AutoCAD users have reported the issue.  Since there is interaction between Electrical and AutoCAD, there is a possibility that some sequence of commands on the Electrical side adversely affect the AutoCAD side and change the FILEDIA setting.  There are certain commands within Electrical that temporarily switch the state of the FILEDIA variable, but they are supposed to switch it back after the command sequence is completed.  

All input is welcome.  Fixing issues is usually the easy part.  Being able to reproduce the issue so the deveopers can troubleshoot it is the bigger problem.  That's why they ask us to document every step that leads to the issue, and provide drawings if possible.