Hello!
We use a fairly large amount of macros at my company, but I'm having a very strange issue after upgrading from Excel 2010 to Excel 2013. All of my macros have broken! For example, the following macro is used to "merge" two columns of data. This macro works in Excel 2010 but not in 2013.
Any help would be greatly appreciated!
Please Login or Register to view this content.
Please explain what "broken" means.
Does the code run?
Does it produce error messages? If so, what do the messages say?
Does it produce unexpected/wrong results?
Does it hang?
Also, your profile says you use Excel 2003. Please update your profile to reflect what you are currently using.
Jeff
| | |·| |·| |·| |·| | |:| | |·| |·|
Read the rules
Use code tags to [code]enclose your code![/code]
I tested your code with excel 2013, no problems on my test sheet
If solved remember to mark Thread as solved
After doing some troubleshooting, it appears that the issue with that I'm having does not stem from the upgrade to 2013, but rather from the fact that I put all of my macros into a "Personal.xlsm" file. When I run the above macro in a regular Sheet or Workbook, the results are fine, but when I run the macro in my Personal.xlsm file, the results are incorrect.
MY TEST SHEET:
Column A1: Column B1:
A "1"
A "2"
A "3"
B "4"
B "5"
C "6"
EXPECTED RESULT (Works when NOT in Personal.xlsm: )
Column A1: Column B1:
A "1" "2" "3" (in single cell)
B "4" "5" (in single cell)
C "6"
RESULT WHEN RAN IN "Personal.xlsm" File:
Column A1: Column B1:
A "1"
A "1" "1" "2" (in single cell)
A "3"
B "4"
B "5"
C "6"
Last edited by OfTheNaveed; 05-13-2014 at 10:40 AM.
What kind of module is the code in in the Personal.xlsm file? A Module, or a Sheet?
You should make Range references explicit. Without qualification it will default to the sheet which owns the code module. If it's not a sheet module but a Module module, then it should default to the active sheet. For example, you may need to change
toPlease Login or Register to view this content.
It may be worth your while to stop the code on that line in debug mode and see what the code thinks the active sheet/active workbook is.Please Login or Register to view this content.
The macro was stored in "ThisWorkbook" on the Personal.xlsm file. I moved it to a Module and the code (and all the other macros) works flawlessly.
Thank you so much for the help!
There are currently 1 users browsing this thread. (0 members and 1 guests)
Posting Permissions
LinkBack URL
About LinkBacks
Register To Reply
Bookmarks