I am working in ProjectWise, but when I tried this outside of ProjectWise, I received the same error message.
I only mention this because the filename listed in this image is a dead giveaway to this being a file in ProjectWise, and I don't want anyone to follow that path. ProjectWise is a red herring in this problem and can be ignored. Note that I also learned a while ago, that for this to work in ProjectWise, you need to check out the xls file along with the csv file.
However, I recently had the 64 bit Office 365 on my PC and even after reinstalling ProjectWise, the office Integration is not working 100% as it used to. Likewise, outside of ProjectWise, even Windows is having issues recognizing that I now have 64 bit Office and not 32 bit Office.
I suspect that this issue is related to that problem.
Before this upgrade, this process worked just fine.
Is these someplace in the registry that I can fix this so that the remap tool recognizes my 64 bit Excel is an acceptable application for the remap tool. Without this, I am down to manually editing a remap csv file and this is far from ideal.
I found the solution, and my belief this was a Windows issue was correct. In Windows 10, getting to the "What program opens files with this extension?" setting is not as easy as I seem to recall it used to be.
I had previously fixed xlsx files but had not fixed xsl files.
I went to the file's folder and in its properties dialog box, I was able to change its default application to my 64 bit Excel application and then, the edit remap button worked as before this whole thing went south.
Charles (Chuck) Rheault CADD Manager
MDOT State Highway Administration Maryland DOT - State Highway Administration User Communities Page
Answer Verified By: caddcop
Good to hear that you've been able to resolve your issue. If it was a ProjectWise / Office Integration issue their Content Management forum. Otherwise the following Wiki article might assist in the future to fix basic Windows file associations.
RegardsAndrew BellTechnical SupportBentley Systems
The link for Windows 10 is inadequate. It send you to the "new" App style interface, but it does not recognize all programs and won't allow browsing to programs it does not recognize, but are installed on the PC. Using the File Properties seems to be the most direct method of changing or fixing a bad file association.
BYW, Windows 10 is horrible when it comes to accessing two programs with identical exe filenames. We have to use two versions of Power InRoads due to legacy projects, and outside of ProjectWise, it is impossible to even get an Open With right click menu to support both version. It always uses whichever was loaded last, even if you browse to the other version every time.
I did find some type of freeware tool that allows you to get around it, but its totally not authorized by our IT department, so we cannot use it.
I dont get same problems as your having ... we have win 10 and I have V8i ,Connect and ORD versions msnt and I can open "with " as for ms office were now using the 360 version and most of my short cuts didnt work and had to remake them.. but only 360 version of office suite is on pc maybe thats the big difference.. but my IT didnt make any announcements or work arounds
To quote the Irishman movie of late, "It is what it is "...
Lorys
Started msnt work 1990 - Retired Nov 2022 ( oh boy am I old )
But was long time user V8iss10 (8.11.09.919) dabbler CE update 16 (10.16.00.80)
MicroStation user since 1990 Melbourne Australia.click link to PM me
Keep in mind, I had the 32 bit office 365 installed but was having some minor issues and when I tried a repair, it made things worse. Apparently, while I was allowed to be a local admin on my PC, some of the things needed to do an office repair were still blocked.
So I had our IT group uninstall and reinstall, but they also upgraded me to 64 bit office 365 in the process. As a result, many of my old "open with" settings were now looking for the 32 bit version. I had to manually go through each "program associated file types by extension" to repair their association. In Excel and the remapping feature of MicroStation, since it still uses XLS and not XLSX files, it was still broken, but the error message was not the same as other times that a file type was not fixed. I only realized what the possible issue was when I notices an XLS file was missing the Excel icon in Explorer. I don't have that many XLS file still around, having upgraded most to XLSX.
I guess it would be beneficial if we could upgrade the remap tool to use an XLSX type of file, too.