How do i make the connection between visual basic and open office base, I can only find tutorials showing how to connecting to access.
Any help?
Here is a link that may help:
Working with Open Office in .NET
Its a bit older, and somehow even older than that:
http://opendocument4all.com/content/view/68/47
and then the general information on the API
http://wiki.services.openoffice.org/wiki/Documentation/BASIC_Guide/API_Intro
Related
I need your help on a generic question. I am using Visual Studio 2012 to develop my Windows Forms Application that is running only on my machine locally to support my work. I have Windows10 and Office2016 installed. My Application interacts with MS Access (via System.Data.OleDb) and Outlook+Excel via Office.InterOp. Fine.
Today I received the information that our Company is rolling out Office365 and I started researching how this could impact my development work. I am not a programmer (more business) but always try to teach myself. But in this case I have no clew what all that means. I read about registering my Application before I connect to Outlook, Outlook REST API and many other things.
So my questions are:
Will my Application work the same way after migrating to Office365 (InterOps) ?
Is there a good tutorial out there that helps me getting started?
I really appreciate any help and guidance on this. Have a great weekend. Thanks
First what is yoy current version of Office you use ? Then do you know if your compagnie will move to office pro plus ? (I suppose yes)
Even if you pass to Office ProPlus the interop will still work, you should after starting to move you app using Graph API, but this API is to interact with the Office 365 data, not the Office App, it's in this case you register your app o the Azure Active Directory to have the right to use Office data
It is working on the web but not on the desktop. I have read all the available threads already but I am still not able to figure out the reason
Please guide, any help would be appreciated
My Manifest is compatible with outlook 2013 or later, what can be the reason?
Do you get any errors?
The Troubleshoot user errors with Office Add-ins page describes the information to help resolve common issues that your users or you encounter with an Office Add-in.
You can also use Fiddler to identify and debug issues with your add-ins.
I am trying to understand how to develop add-ins/macros in JS for Office, do I need VSTO for it or does it run from Office somewhere?
I did understood that Microsoft is making the first steps toward replacing VBa with JS and impemented an API to develop macros in Office.Js simmilar to the one Google has for it's Docs. But where can I find a development enviroment for Office.js?
The new web-based add-ins are basically a web application executed in the context of the Office application, either on the Desktop (by embedding a browser, IE11 at the moment) or in the browser (Office Online) where everything is web-based already.
The add-in can be hosted on any web resource you like. You just need to specify a source location URI.
Settings and metadata of the add-in are defined in a manifest file. The article Office Add-ins platform overview describes it very well.
Development can be done in any editor or IDE suitable for coding web apps. There is no Alt+F11 VBA IDE anymore, but you may try the Script Lab add-in, a Microsoft Garage project that allows you to try out some code directly in Office and share code snippets. It includes a great collection of sample code too.
The new WebApplications are hosted on a Webserver. You can develop Office Apps with Visual Studio.
Here is a good course for developing Office Apps including an overview of the Javascript Office API:
https://mva.microsoft.com/en-us/training-courses/introduction-to-office-365-development-8329
New project in Visual Basic using Visual Studio 2013.
Want to add the "Microsoft Internet Controls" component but I can't find it.
What am I missing?
This is the second link on Google:
http://answers.microsoft.com/en-us/office/forum/office_2010-customize/cant-find-reference-to-microsoft-internet-controls/e138ff0c-8046-47b1-9c0c-ac28cebe3c7a
Apparently it may have been renamed "Microsoft Browser Helpers" and you may need to add a reference to "ieframe.dll".
If you need FTP, it is fully supported in the .NET framework. You could start with the examples on MSDN: https://msdn.microsoft.com/en-us/library/ms229718%28v=vs.110%29.aspx
The inet1 Internet Transfer Control is installed with MS Office. Install it and you should have no problem having it become available to use in Visual Studio etc.
It's old but still completely useful in apps. It did all the FTP and HTTP calls for a web crawler I wrote years ago and was fast and completely error-free when crawling 100s of 1000s of web pages at a time while I slept. I'd use inet1 today if I was writing an app that did huge amounts of internet calls as quickly as possible.
I'm trying to use MS Office Name.dll as a COM object.
I found some help in these links to do something like this in web browsers:
https://msdn.microsoft.com/en-us/library/office/ms455335(v=office.14).aspx
http://mcgivery.com/displaying-a-users-lync-status-using-namectrl/
http://blogs.msdn.com/b/tomholl/archive/2013/03/02/integrate-lync-into-your-intranet-sites-using-the-namectrl-plug-in.aspx
name.dll basically allows me to get presence information from MS Lync and display a contact card.
I was able to successfully create a test Windows Form application that references name.dll. VisualStudio creates an Interop for me and i'm able to use the class NameCtrl.
The project worked fine and my test aplication was able to display the contact card, but only when working with an old version of Office 2010.
When upgrading to Office 2010 SP2, it didnt work anymore. When using Office 2013, it never worked.
I can actually instantiate the object successfully, but the object's property 'PresenceEnable' is always 0, and trying to display the contact card throws an exception "E_ACCESDENIED 0x80070005". In these not-working environments, using the webbrowser (IE/ Firefox) still works fine.
Does anyone know what to do to make it work?
Why did it only work with an old version of Office 2010 and stopped to work with newer releases?
I talked to a Microsoft Office Engineer and he told me this dll was not meant to be used that way: it's only meant to be used inside web browsers.