So I was given a access 2010 application. I'm trying to deploy it and it was developed in access 2010 sp2. The end users do not have access on their laptops so I installed access runtime 2010. I'm now seeing references errors and I'm guessing its because the development happen in 2010 sp2, and the runtime is runtime 2010 sp1 (not sp2). Is there a way that I can see what references are actually being used for the application?
Related
I have problem with Microsoft Office 365 and Microsoft Access database engine. I used Microsoft Office 2016 with Microsoft Access database engine 2010 Redistributable which works fine, but yesterday i switched to Office 365 and i get error: System.InvalidOperationException: 'The 'Microsoft.ACE.OLEDB.12.0' provider is not registered on the local machine.'
I read some microsoft docs and another web sides witchexplains this problem, but nothing work to me.
Now I have installed Microsoft Access database engine 2010 Redistributable 64bit and Microsoft Access database engine 2016 64bit
I would like to point out my office 365 Bussines is 64bit, Windows 10 is 64 bit and visual studio 2019 is 64 bit
Did anyone know, what i have to do?
As part of a project, I've implemented an application in VB.Net that was connecting to a MS Access 2010 database to read/write data. It was working perfectly, but recently some people recived an upgrade to their Access application and they're now using "Access 2016 32-Bit" and now when they run the application it's throwing the error message "Microsoft.ACE.OLEDB.12.0 provider is not registered in the local machine".
I went back to look if the driver was indeed in their machines and it is.
The application was compiled using "ANY CPU", I change it to be x86 and it's still not working.
I've checked several threads regarding this same issue, difference conditions perhaps and I've read several solutions, mostly directed to 64-bit.
For example this thread: 'Microsoft.ACE.OLEDB.12.0' provider is not registered on the local machine
I see several people install the Microsoft Access Database Engine 2010 Redistributable and the 2007 Office System Driver: Data Connectivity Components and it worked for them.
However I'm not sure if this will apply for Access 2016 or if it will mess up with the current installation users have on their computers.
Any thoughts?
Thanks in advance for any help anyone can provide. If there's more info required let me know.
I have a database system that I use for work which is self developed. I use an Ms Access database to collect the information from the form. The application works fine and I have no issues with it.
My company is taking my desktop PC away from me and replacing it with a laptop, however they've pre-warned that office will not be available on this laptop as we can hot desk if office applications are required.
The question is, will my application still be able to databind to the Ms Office (.accdb) database and write via SQL, even though office is not installed?
Your VB.NET application can manipulate Access .accdb database files without having the Microsoft Access or Microsoft Office applications installed. You do need to have the Access Database Engine installed, which is available as a free download here:
Microsoft Access Database Engine 2010 Redistributable
My situation is that I developed a .NET 4 based MVC2 web app, and now I have to deploy it on a Windows Server 2003 that has standalone SharePoint 2007 living on it. My quick research shows that SharePoint 2007 doesn't play with .NET 4. So my questions are:
1) Will SharePoint 2007 break if I install .NET 4 on the server? As far as I know .NET versions were backwards compatible...
2) Is it possible to deploy the .NET 4 assemblies with my web app without actually installing the framework and registering it.
3) Any other tips and advises on resolving this situation?
SharePoint wont'break if you apply latest service packs + cumulative updates to it.
At least I have such a combination running on my servers right now.
It would be a problem, if you tried installing .Net4.0 on the same machine prior to "Infrastructure update" of 2009 (or maybe before SP2?), since, as it was said "SharePoint stored some references to .net4 classes in the configuration database", whatever that means.
I'm relatively new at creating custom content for Sharepoint 2010 and have been having some difficulty understanding how to get non-design related components (ie. web parts, custom classes, ...) into a Sharepoint site. I have created a new visual web part on the company's development server and deployed it successfully from Visual Studio 2010 and also packaged the solution into a WSP file.
What is the best way to go about getting that web part onto the production server? There is currently no Visual Studio install on the production server but from searching around I get the feeling that it might be possible to do this remotely using Powershell or STSADM. Has anyone faced a similar situation?
Use PowerShell. Stsadm is considered to be obsolete and is included in SharePoint 2010 only for backwards compatibility with SharePoint 2007. So, since you are new to SharePoint, pretend Stsadm doesn't even exist.
My PowerShell scripts keep evolving, but they are based on samples from Ted Pattison:
Chapter 2: SharePoint Foundation Development (scroll down to Using Windows PowerShell Scripts to Automate Tasks in Visual Studio)
PowerShell Boot Camp for SharePoint Professionals