![excel 2016 crashing windows 10 open blank workbook excel 2016 crashing windows 10 open blank workbook](https://i.ytimg.com/vi/HFzi1TYSQk8/hqdefault.jpg)
- #EXCEL 2016 CRASHING WINDOWS 10 OPEN BLANK WORKBOOK 64 BIT#
- #EXCEL 2016 CRASHING WINDOWS 10 OPEN BLANK WORKBOOK UPDATE#
- #EXCEL 2016 CRASHING WINDOWS 10 OPEN BLANK WORKBOOK CODE#
- #EXCEL 2016 CRASHING WINDOWS 10 OPEN BLANK WORKBOOK PROFESSIONAL#
Yes, you can do this to some extent through hierarchies these days, but you may not want to pay the price in either memory or potential user confusion of having a visible, functional hierarchy that shows the reporting structure from 18 months ago and 3 years ago. If there is a corporate restructure you can keep a snapshot of what the rollup structure was back in the day. (h) I almost forgot time based consolidation trees. (Again this advantage isn't as relevant to me now that I use Arc.) (g) You actually have a real honest to glub find and replace facility. xdi as well, but if you're maintaining the dim via an. xdi but if you're generating the structure in Excel anyway then they may as well be. (e) Formula based elements in a dim, especially for a time dimension. When I have a whole string of rules which are similar but not identical I can generate them by Excel formulas with variable expressions off to the side somewhere. (c) Colour coding blocks of rules and elements to make it easier to see where you are, especially in really long dimensions. xru I can write the documentation of the whole model in a separate sheet and not need to go hunting for it if I wish to do that. This is less of an issue now that I use Arc which is finally oh finally a good editor, but even so in an. You've always been able to add comments to rules, but there the problem was that the classic rules editor sucked and the allegedly advanced rules editor wasn't much better. It's far easier to include information about why particular consolidations or rollups are structured the way they are, and have it embedded inside the dimension sheets rather than external to the model. (b) You can embed metadata about the model.
![excel 2016 crashing windows 10 open blank workbook excel 2016 crashing windows 10 open blank workbook](https://www.easeus.com/images/en/data-recovery/drw-pro/repair-ms-office.png)
You aren't constrained by DimensionSortOrder. (a) You can force the order of the elements. The reasons I still use them when I need them: Aren't they pretty much obsolete nowadays ? Opening the XDI file in excel directly as an excel document and then using the developer/ Dimension Save option.Ĭan someone explain to me the relevance and benefit(s) they bring ? Then I can have a better idea on this. They are maintaining the system using the work around mentioned by others above, eg.
#EXCEL 2016 CRASHING WINDOWS 10 OPEN BLANK WORKBOOK CODE#
When run directly on the server we got a VBA Automation Error code 440 before the system close.Ĭreating a new XDI/XRU file in a blank folder works fine, (eg "Dimension New") and loads into the system. We have found that if the local server data directory, once an XDI or XRU file is saved in there will cause Excel to completely crash without error messages when attempting to open a file from that folder.
![excel 2016 crashing windows 10 open blank workbook excel 2016 crashing windows 10 open blank workbook](https://www.lifewire.com/thmb/t6nUbAuW6Hgd_9UZJRAyhv8ZI08=/1712x963/smart/filters:no_upscale()/001-microsoft-word-files-wont-open-3540218-fd30da3922414149af0dd0b282e12567.jpg)
They need to use the developer feature as they wholesale change the dimensions used in their analysis, and alternative solutions are not as elegant - eg Dimensional editor is clunky, no desire to use TI scripts and CSV inputs either. This same issue has been reproduced using PA 2.0.8 and 10.2.2 under the O365, using Planning Sample. I have a client with the same issue - opening developer options/ "dimension open" causes excel to crash with Excel O365 and Excel 2019 MSO 64 bit. Is anyone else experiencing this in a similar environment?
#EXCEL 2016 CRASHING WINDOWS 10 OPEN BLANK WORKBOOK 64 BIT#
It could therefore be specific to my machine or, what I think is more likely, there's an issue with the VBA code that reads the list of files in the data directory when it's run by 64 bit Excel. I'm not encountering this with PA2 (the bits that actually work, that is Perspectives and Web but not PAX because, well, Docker), but in the PA2 test environment (on a different machine) I'm using Excel 2016 (Office 365) 32 bit. other than the irritating Extension Hardening warning which of course I immediately turned off.) (Workaround: It can be opened as a regular file, updated and saved as a dimension without any major problem. xdi file.) However once the file is saved, I can't re-open it through Dimension Open because. xdi and I have to manually change to the new. (Although Excel will shove the ever-accursed "Book1" in my face after it creates the new.
![excel 2016 crashing windows 10 open blank workbook excel 2016 crashing windows 10 open blank workbook](https://cdn.windowsreport.com/wp-content/uploads/2018/04/Excel-1.jpg)
If the data directory is empty I can create a new dimension and save it correctly. (b) If the data directory has even a single file (.xdi) in it, Excel will generate an "Automation Error" warning, then crash. (a) If the data directory specified is empty, then an empty list will be shown as expected but
#EXCEL 2016 CRASHING WINDOWS 10 OPEN BLANK WORKBOOK UPDATE#
If I select "Dimension Open" in Perspectives to update an. Note particularly the "64 bit" part which is where I suspect this issue is coming from.
#EXCEL 2016 CRASHING WINDOWS 10 OPEN BLANK WORKBOOK PROFESSIONAL#
I haven't submitted this at this point because I need to check whether this is just a "my machine" thing or something that applies to everyone.Įnvironment: Windows 10 professional 64 bit.Įxcel 2016 ( 64 bit) from Office 365.