I, in fact two end users have seen a strange issue in Excel.
When they CTRL+X to cut some cells and CTRL+V to paste, it does copy/paste, not cut/paste
They said it is related to the new version addin I built. I do not use or change anything about copy/cut/paste in my code at all. I suspect it is some options in Excel, but not sure what it is.
Do anyone know how to fix the cut/paste issue in Excel?
Edit
my addin is written in C#, Excel DNA, NetOffice, Add-In express. It is a xll addin with ribbonX and also has UDFs. There is no VBA except during install/uninstall, I use VBA to install xll and xla.
xla returns descriptions for UDF and register help topics.
thanks
This is related to skype, not my code or anything. Once skype is unistalled, copy/cut/paste works fine. see http://answers.microsoft.com/en-us/office/forum/office_2003-excel/excel-2003-moving-border-when-copying-not-working/f55b0eab-13ff-489c-bd2d-d16937cd02ec?msgId=19e8fa3b-0ac2-4af0-bde7-5ac52d131f10
Related
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.
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.
I created some Excel macros with VBA, saved it as .xlam file. I copied the file to another computer (running Excel2013) and put it in the following folder:
%UserProfile%\AppData\Roaming\Microsoft\AddIns
I enabled the Add-In from Excel > File > Options > Add-ins. Now I want to add those macros to Quick Access Toolbar(QAT). In the QAT options, I choose "Macros" from drop-down menu. The macros didn't show up as I had expected. The list is blank.
My subs do not have parameters if that matters. I have searched the forum and Google with no luck. What else I can check? Thank you!
I experimented with one of my own add-ins. All the subs in a general module were visible; however, none of the functions were. (Even the functions with no parameters -- tested by changing Sub to Function temporarily. The switch resulted in that macro disappearing from the macro list.)
Since you don't mention if there was this issue on the first computer; I am assuming that you would see the same thing there, if you checked.
If you sometimes need a return value from those macros, could you create "calling" macros? Subs which call those functions? If you never need a return value, I would recommend just changing the designation from Function to Sub on the relevant macros.
You could also check out this answer on how to add a button to the excel ribbon via add-in code. This could be useful if you plan on moving the add-in between multiple computers.
Foolish me!
I saved the macro module into personal.xlsb. However, I was trying to export it by creating a blank spreadsheet (e.g. "Book1.xlsx") and save it as Excel Add-In (e.g. "Book1.xlam"). Of course the Book1.xlam won't contain any macro!
I apologize for newbie mistake.
I wrote a macro that consolidates two files into one new file on excel 2007. I sent it to someone who tried to run it on his excel 2010 and he received the error in the Title of this question. We have tried to
make sure he had the Solver addin activated and a reference to it checked
pasted this in the immediate window application.run "solver.xlam!auto_open"
I tried to disable the Solver addin on my end, save and resend to him
make sure macros were enabled
The solver addin isn't even necessary for this program, as far as I can tell. I should mention that the macro works great on my excel 2007.
Thoughts?
SOLVED: The strangest thing happened. When the workbook got emailed the button the macro was originally assigned to got changed to solver.xlam. All I had to do was instruct him to reassign the button to my macro. How odd is that?! Curious if anyone else has experienced anything like that.
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.