I want to know if there is way to delete/remove "Add-in" i have added in my online excel file (o365),currently I see remove (x) button in excel desktop app and it works like a charm it also has a reload option to just reload any particular "Add-in".
None of the two options (delete & reload)I could find in Online excel version, although for reload a simple f5 is enough,I am having a difficult time figuring out how to disable a addin i added for experimental use,I end up deleting the whole excel file which is very ridiculous,hope I am missing a simple trick and anybody can help me through.
One thing to add to Sudhi's answer: to fully remove an add-in from the document (rather than just make a task-pane invisible, but still keep the underlying application there, and still have it persist its settings and bindings and etc.), you would need to use the Document Inspector: http://www.makeuseof.com/tag/remove-hidden-personal-data-microsoft-office/
The only way is to open the document in desktop and remove the add-in. We have a roadmap item to allow closing either through close button or API. Until then I think closing in desktop is the only way.
Related
I googled around and found no answer for what I think should be an obvious question/problem, so I'll ask here.
I have an ExCel spreadsheet that I want to share with a couple other guys. Version, as far as I can tell, is "Office 365 ProPlus" (sorry if that's wrong, I'm a linux guy). I do the vast majority of the writing/editing, the other guys mostly just read it. I put it on a shared drive. But when they open it, it opens in edit mode and I'm locked out because one of the other guys (who just wanted to read it) opened it and the default open mode is edit.
I want to change the default open mode to be read_only. If I want to open for edit, I don't mind clicking a few times to get to that point. But what I can't have is being locked out because the read_only guys have it locked. If they have it locked because they're making changes, that's fine. But for the 95% of the time, where I write and they read, I don't want them to unintentionally lock the thing when all they want to do is read.
Is this sort of thing possible ? Can I configure this ?
You may save your document as "Read-only recommended" and get your friends to open it read-only whenever they do not need to edit the document:
For the new versions (2013 & 2016), while Saving or Saving As your file press Browse button, go to Tools | General Options and select the Read-only recommended check box. If you want you may enter a password too. After this, the users will be recommended to open the document as read only; if they want, they may still open the file in edit mode.
In addition you may use the shared workbook feature of Excel which allows multi users to edit the document at the same time. And using this way you may track which changes are made when and by whom too.This feature can be activated using Review / Share Workbook button. If you have a newer version of Excel, this button is hidden, you may unhide it using the instructions here: unhide shared workbook
Old post but I just had the same question and landed here. I was also suspecting the Office version but it turns out that's not it. I figured it out that instead of going to the File-Properties you have to go to the "Save As..." dialog box, and there, next to the Save / Cancel buttons, is the Tools... dialog where you can set a "Read-only recommended" check mark.
I think the implication is that it's not a document property, it's a windows file property - that's why it's not in the File-Options menu.
After I found it, I remembered that this is how I always used to do it in old versions of Excel many years ago, so it's really unchanged.
I am trying to develop an Excel add-in by using JavaScript API for Excel.
I can already make some samples run, launch debugging under Visual Studio. Every time when i launch debugging, it opens a new workbook of Excel.
However, most of time, I need to debug an add-in on an existing workbook. For instance, here is an add-in sample, which opens a blank workbook and adds blank sheets to it. However, I want it to add blank sheets to an existing (opened) workbook. Does anyone know what I should set to debug it on an existing (opened) workbook? Should I modify some lines of code?
Edit 1:
From http://dev.office.com/docs/add-ins/get-started/create-and-debug-office-add-ins-in-visual-studio
To use an existing document to debug the add-in
In Solution Explorer, choose the add-in project folder.
Note Choose the add-in project and not the web application project.
On the Project menu, choose Add Existing Item.
In the Add Existing Item dialog box, locate and select the document
that you want to add.
Choose the Add button to add the document to your project.
In Solution Explorer, open the shortcut menu for the project, and
then choose Properties.
The property pages for the project appear.
In the Start Document list, choose the document that you added to the
project, and then choose the OK button to close the property pages.
Here is the resulting configuration that you should see:
After that just press F5 (start debugging), and you should be good to go.
~ Michael Zlatkovsky, developer on Office Extensibility team, MSFT
For anyone else running into this same issue (i.e. tying to set up an existing worksheet for debugging) without having to jump through 3 hoops to insert the add-in every time, this worked for me:
Set the Start Document to "New Excel/Word/etc Document"
Hit F5 to start debugging.
The resulting new document will be read-only and it will be in the Debug/Release folder.
Close the document, don't save it.
Copy the document to the folder where your Web Add-In manifest is and renamed it to whatever name you prefer.
Uncheck "Read Only" int the file's properties.
Set the Start Document as described by Michael in his response above.
If you start debug now, the add-in "should" load automatically. If you start without debugging (Ctrl + F5), you should be able to close the document and open it (or a copy of it) from anywhere in the PC and it should load automatically. You can even make changes to your JS code and reload the taskpanes/dialogs and it should take effect.
What did NOT work:
Using a blank start document and saving it after inserting the add-in. Once you save it, it loses its connection to the developer add-in.
If you start any document in debug mode and save it, it will NOT work the next time! If you want to make any changes to it, DO NOT start in debug mode.
I am not sure if any of these quirks are by design or if a Windows/Office update messed it up for me. Regardless, this is a very painful experience compared to developing VSTOs.
I've started using Crystal Reports recently. Have been able to create a report and mostly done with it. But suddenly I started to lose any change made inside a textbox object. I edit a textbox, save the report and close it. And then I reopen it to see that the change hasn't remained. I restart the Visual Studio and even the machine but nothing helps. I use VS 2012. Has anyone experienced anything like this?
In the report preview see if the checkbox "Save data in the report" is checked. If so, try unckecking this checkbox. It is causing me some trouble to save the report crashing Visual Studio interface.
In fact I found the reason for the problem. This happens when I try to save the changes while the focus is on the edited object, in this case textbox. But if I click somewhere else (in order to lose focus on the edited textbox) before saving, then the problem gets solved. Happy to have found it.
Welcome to the club :)
Crystal Reports can behave very strangely in some cases. For instance, some times when i edit a report file in Windows XP, it crashes the interface and corrupts the file when i save it. The same problem doesn't appear in Windows 7. However other strange things happen in Windows 7 also.
I would recommend you to
Always apply the latest Service Pack available for the Crystal Reports Engine.
Always check if the asterisk sign disappears from the opened report file when you save it (some times it doesn't when you hit save and it does when you hit save all and vice versa).
Always backup your report files once in a while because to recover a corrupted file is a very hard task.
You can try the following to find out what causes the problem
Create a new blank Windows Forms project, add the same report file there and check if it behaves the same.
Create a new blank report file and check if a change in a field behaves the same way after saving it.
Try it on another OS.
Go to Database | Verify Database and make sure the database is up to date.
Also Go to Database | Show SQL Query and reset the query. Now enter in the Selection Formula again and save.
Updating the SQL will replace the Selection Formula.
Good luck,
When typing in the editor it puts me back on the end of the last word.
For example, I want Sub Entername()
If I'm not typing quickly enough it goes: SubEnterName().
How do I turn this off.
I've heard of this problem before. Try these steps:
Close down excel.
Open it first it in safe mode (type "excel.exe /s" in the run box).
Open the VBA Editor and attempt to write a macro. The issue should not occur
Close down excel and re open it normally
I've heard these steps have fixed this issue before for others.
Are you using any VBE addins like Smart Indenter or Code Cleaner? Remove Code Cleaner and install it only when you are going to use it, then uninstall it when you are done. I had the same problem and Code Cleaner was the culprit. I believe it might be the two of them together that causes it.
For reference:
VBA Code Cleaner
Smart Indenter
This issue is because of a COM Add-In called 'Load Test Report Addin'. to disable it, do the following:
go to Excel Options -> Add-Ins and choose Excel COM Add-ins from bottom drop down and press Go... button. then uncheck the 'Load Test Report Addin' item to diable it. this will clear the problem!
To prevent auto refreshing and deleting back-spaces in VBA editor, you should make sure that all forms or reports that have On-Timer Event Procedures are in design view or the code should be turned-off (i.e. converted into comments).
However, it is better to make sure that all forms and reports are in design view which means none of the On-Timer codes are executing.
I hope this helps.
Shafiu.
Do you have AutoSave turned on? I had a file doing this just now. While typing, as SOON as I stopped, AutoSave was working away - (inadvertently, I'm sure) this was causing VBE to kill spaces.
Did two tests:
-Moved the file off Sharepoint onto my local machine, worked fine
-Turned off AutoSave on the Sharepoint copy, worked fine
Is there a way to convince the VBA editor in Excel to stop auto-formatting lines to remove the space at the end when I pause in my typing for a quarter second?
I had this exact problem and the following worked for me.
Click the Microsoft Office Button, and then click Excel Options
Click the Add-Ins category
In the Manage box, click COM Add-ins, and then click Go.
Look for an add in called 'Load Test Report AddIn' then uncheck it
restart excel
This addin is installed with VS2010 Beta2
In Excel 2010, toggling Design Mode button on the Developer Ribbon Tab solves the problem for me.
I've definitely had that issue before, where the vba editor would format as I was typing (not just when I went to another line). For me, it seemed to be related to a Microsoft Web Browser control that I had in an open workbook. When I took out the web browser, the VBA editor started acting normally again. I have no idea why that worked, but it did. Now I avoid using that control in my workbooks.
Something is causing your spreadsheet to recalculate while you are in the VBA Editor and this 'compiles' your code and thus strips the spaces. You need to stop the cells recalculating while you are editing. Turning the calculation to manual in the spreadsheet.
Tools > Options > Calculation should do the trick.
I noticed this when I had cells recalculating thanks to a DDE connection.
There is sort of a way to turn off the auto-"correction" in the VBA Editor.
Tools Menu -> Options -> Editor Tab -> Clear the Auto Syntax Check box
Sadly, this won't solve all your problems, as the VBA Editor tends to have a mind of its own, for better or worse.
Taking it out of design mode fixes it every-time on vba2003 - its was driving me crazy at first ... i did notice it might have something to do with the web control but when i take it out of design mode it works fine ... just toggle that to get it to behave :)
I have had this same problem several times recently, and has driven me crazy.
After reading this post all the different fix-ups mentioned (none worked for me), I recalled I have been playing lately with Internet Explorer Control, opening Internet Explorer from VBA.
This is mentioned in some of the answers in this post.
This got me in the right path and, in order to fix it, I had to first delete all iexplore.exe instances (alt+control+delete), closed Excel and open excel again.
(iexplore.exe had been opened invisible from the VBA code, and I didn't know they were running)
That fixed the bug.
I have been programming quite heavily with VBA for over 4 years, and never had this problem.
Just a couple of weeks ago I started using IE control, and I started getting this problem...so in my case I can only assume the bug is directly related to the IE control.
I am running both excel 2003 and 2007 in same PC at the same time, and the problem only happens with excel 2007.
None of the above for me.
I had a Application.OnTime timer that fired every second and this triggered a recalculation of something: commenting it made my day.
This has started happening to me recently after adding a Timer event to an Access 2007 form. The VB editor "finalizes" the current line (as if you had moved the cursor off of the statement; I have auto syntax checking off) each time the event fires (initially I had it set to 1 second, now it is set to 5 seconds, and the behavior scales accordingly). In order for the event code to execute, the application has to ensure that it has been compiled. Presumably, the editor needs to be in a "sane" state to do this, as it probably has to check for code dependencies among modules. Note that the behavior occurs regardless of whether any dependent code is actually loaded into the editor at the time. Note also that resetting the execution state doesn't affect the timer event firing. As a practical matter, one could close the triggering form, switch it to design view, set a breakpoint in the triggered code, or increase the timer interval while working with the editor.
In contrast to abhishek's comment, changing the settings of Tools/Options.../General/Compile On Demand and/or Background Compile did not affect the issue.
If it helps, none of the previous answers solved mine. Only solution appeared to be to close the xls file and reopen it. Frustrating to have to do every 30 mins but at least it works. Would love to know why it's recompiling and cleaning the text... should really be an option to disable the text cleanup but couldn't find it.
Turn off Tools > Options > General > Background Compile. This solved it for me.
This is a long standing problem that could have various causes. I had this same issue occur in the Access VBE (so naturally the Excel answers weren't relevant). After a LOT of digging I finally got it fixed with the solution below. First a recap though:
If you are here because of this issue in Excel, try the solutions above first. To summarize:
The most common issue in Excel is that the Design button is toggled. Toggle that and see if the behavior changes as submitted by Dmitry Frenkel above
If that doesn't work, check for the "Load Test Report" AddIn as mentioned by Ade.
Those are really the two main causes in Excel, but if neither of those solutions work, then scroll through the rest of the solutions here. All are valid possibilities for the cause. In Access the cause is pretty straight forward. It's a timer issue on a form somewhere. I found this solution from here by User Kevin K. Sullivan.
Copy the following line of code onto the clipboard. (You might need to
paste it into a text editor first and coerce it onto one line, depending on
your newsreader. It must be one line.)
For i = 0 to Forms.Count -1: Debug.Print Forms(i).Name, Forms(i).TimerInterval: Next i
Switch to Access.
Press Ctrl-G to go to the Immediate Window.
Press Ctrl-V to paste in the code.
Press enter to to run the code. All open forms will be listed. Any non-zero timer intervals are your culprits. Simply close that form (It may be invisibly open from another process than the one you thought you were dealing with).
I think the solution for Access here is what the user Dom was trying to say above. I guess the down votes were because it wasn't explained very well and/or because he was speaking of Access when the OG issue was in Excel. Regardless, he is likely on point if you are here because of the VBE in Access.
I hope this helps people. I know I kept finding this page when researching this issue, so that's why I thought I'd update this solution here.
I hit this problem today on a fresh install of Excel 2010 Beta 2. None of the above made any difference, but going into the trust center and disabling all application add-ins fixed the problem for me.
I have Office 2010 Pro and I had the same issue. As I type the space between each word was being deleted. After trying each of the options turning them on and off the only way I found working was to disable the Winzip Courie(excel) add-in. This is done thru the Options dialog box Add-Ins section.
In office 365 I had the same issue - what worked for me is I saved the file with a different name and when I re-opened the new file the problem went away.
I found this issue pops up when I had AutoSave on. Turning that off let me code without it compiling every second.
I don't think I've ever seen the VBE remove a space when I've stopped typing. It will remove trailling spaces from lines if you move to another line, but that's something different and not behaviour that I think can be altered.
The removal of spaces in the VBA editor for Access occurs when a form is open in Form("Execute") mode. This is probably due to background executions based on "On Timer" methods. Close the form in Access solves the problem in VBA.