Diffrence between opening excel file path with or without quotas - excel

I got a recent problem with Excel.
We are working with macros and it is in a Citrix envoirment.
We are filling an Excel sheet with data that works perfectly fine.
But our coworkers have made themself templates which are getting filled.
Now if you choose the template to be filled it is first pretty slow and then actually freezes/crashes.
What I have recognized when you choose the template like \server\folder\template.xls it crashes but if you choose it like "\server\folder\template.xls" it doesnt but the templates seem not to work as their saved macros won't run.
But what else diffrences between those two Options.
Is it really only macros?

As it seems, we had a problem with the excel Installtion.
There was a problem between Excel 2016 32bit, Excel 2016 64bit and Excel 365.
We made a new clear installation with excel 365 and it worked again.
Therefore still thank you for your help and Ideas.

Related

Excel Macros not visible after Office update

I have a workbook in which I consolidate data from various CSV files. There are a number of macros in this file including ones to add new sheets to the file, which is on a shortcut key Ctrl+Shift+N. This has been working perfectly for many years. This morning the shortcut key does absolutely nothing. If I go to the Excel developer tab and click on the Macros button, the list of macros is empty. However, if I open VBA I can run the macro from there and it still works perfectly.
I run Office Professional Plus 2019 and it ran an update yesterday. Does anyone know of a new setting introduced that may hide the macros in Excel itself. Note that macros are enabled on this workbook.
Just for closure should someone else stumble across this. The problem was related to the specific file. It somehow got "partially" corrupted. Still worked and could fire macros from VBA IDE as well as linked buttons, just not with shortcut keys as macros not "visible" in Excel view. File degraded further to a point where it could no longer save.

Issues switching between different versions of Excel

We recently had a new employee join our (very small) company, and he is using Excel 2010 while the rest of the office uses Excel 2016.
When he attempts to run a macro which draws a chart, he gets an error message that says:
Compile Error - Method or Data member not Found
However, this error message doesn't appear when I run the exact same macro in Excel 2016.
The line of code which appears to be throwing up a problem is the following:
ActiveChart.FullSeriesCollection(1).Format.Line.ForeColor.ObjectThemeColor = msoThemeColorText2
Has anyone come across this problem before? And is there any quick solution, besides the obvious of switching him to Excel 2016 like the rest of us?
Thanks in advance.

Excel Workbook freezes after saving it on Excel 2013

I am developing an excel "application" that will be distributed to a few users, so it has a lot of macros/vba code on it. The workbook is about 2MB right now, so it's not incredibly big.
I was developing it on excel 2013, however my workstation had a problem and I had to work on it from a computer with excel 2010 for about a week. Problem is, when I came back to excel 2013, whenever I try to save the workbook(on excel 2013) it immediatly stops responding. When the program closes, excel is never able to recover anything and says the file is corrupted. The problem simply does not occur on excel 2010, where everything works perfecly and I can save it OK.
Does anyone have any idea what might be causing this? I have tried removing a few sheets and saving the workbook afterwards, to test if a specific sheet was corrupted/causing problems, but even after I remove all the sheets from my woorkbook (and just leave a new blank sheet on it) it still freezes when I try saving.
It's important to note that the workbook in question uses a lot of excel features, meaning it has conditional formatting, defined names, activeX controls, shapes, formulas etc.
Well, I did what Ralph suggested and created a new excel file, then copied everything from the old workbook to the new one. Now it works fine. Apparently that was my only way out, the file was probably corrupted in some way.

Can Excel 2011 and Excel 2016 work from the same macro workbook source on OSX?

This may be extremely specific, but I use macros a lot in my job. We recently got Excel 2016 for Mac in my office, which is universes better than Excel 2011 except for the VBA editor which has taken a huge hit in functionality and ease of use.
Lately, I've been editing macros using my Excel 2011 personal macro workbook then copy/pasting all code over to my Excel 2016 personal macro workbook, which can be a hassle and is prone to error at some point in the future. Is it possible to have 2011 and 2016 source from the same personal macro workbook, so that when I edit in 2011, it automatically changes what is used in 2016?
If someone has a solution for this, this could also potentially be a great way to share regularly updated macros among co-workers.
I think I have to disappoint you. I don't think this is possible especially because with every change of version (from 2000 to 2003 to 2010 to 2013) there have always been changes in the vba coding. On Mac this is even a bigger issue as they have added and reduced the functionalities over and over again. Also a lot of code that works on office for windows is not working on Mac as the functionality of the Mac OS and the Windows OS are completely different. I have been working on office for Mac 2011 for about 4 months with vba and it has been really hard to create some codes which on windows would have worked easily.
Also would I not recommend doing what you want as functions which may have worked on 2011 may not work on 2016 as they have changed/deletet/recreated functions when changing the Office-Versions before. So this might provide a huge resource for errors.
If I'm wrong with all this I will be happy to learn otherwise :)
But as I said, this is just my point of view and maybe someone more experienced might help you out with a solution.

Is Excel Object Model changed in 2010?

I have a very old VB6 application, we have lost the source code. It can call excel 2003, 2007 to
Launch excel
Insert value to the new sheet cells.
I guess it use com to automate the excel, anyway we lost the source code and cannot contact the programmer.
After we upgrade the office to 2010, it cannot insert value anymore, just a blank sheet ....why?
Do anyone have the same experience as me? old win32 program work on excel 2003/2007 , but don't work on 2010.
Attach screenshot for your reference:
when using excel 2007 , it can fill the value to sheet.
when using excel 2010 , it cannot, and the windbg show some exceptions, how can I troubleshoot it?
Even if you could trace/capture, I don't think that would help you much.
Based on the simplicity of the code, you would be better off remaking it from scratch. If it's something proprietary and very useful, you should probably consider having both versions installed at the same time, which has worked for me just fine.

Resources