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
Related
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.
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?
I need advise on what can be best way to setup/configure SHAREPOINT 2010 Environment for 6-members teams (with 3-working at onsite and 2-working at offshore)
Currently I only had two team members but team is now increasing. What we have is DEVELOPMENT SERVER - with Visual Studio and SharePoint Server installed. Developers remote VNC to the box and do their development.
But with number of developers are increasing what should be ideal, so that team can communicate from offshore/onshore
Is this Ideal (installed on each developer laptop)
Visual Studio 2010
and
SharePoint Server (Installed on Windows Server 2008) and developers will use this rather than installing SharePoint locally (enterprise edition is very expensive)
We start to developing with SharePoint 2010 in the team one and half years ago. We try different environment structures for developing, but had many conflicts. Today everyone work in his own environment (HV) with SP enterprise edition, just sharing the code via Team System. The problem is in this set-up the content, everybody has his special content, but if it is critical for you, make backup in every environment.
So we have one SQL server, and for every developer a server with SP and VS.
By the way I think you don't need to purchase SharePoint Server for development environment. If I'm right it is free. You need purchase OS, Sql, VS, but not the SP. Please check with your Microsoft seller.
I'm currently writing a program which will need to incorporate writing its output to a database rather than flat text files.
I know that if you use a Database system like SQL Compact, when you build and publish the program (or just build and distribute), your client will have to download and install SQL Compact Server.
My question is:
When using the built in Microsoft Office exports (like writing a Word File, or Writing an excel file), does the client need to have Microsoft Office installed on their machine to make use of these?
When writing to an Access Database, does the client user need to have Microsoft Access installed on their computer?
I'd appreciate any response.
Yes to Excel. You could create the Access database via ADO or ODBC, and that comes with Windows itself. You could store data from your app there, and the clients would use it through your app (or any other that can connect via ADO/ODBC).
Using the MS Office COM automation requires that the MS Office product be installed on the machine running the automation.
There are third-party code libraries that replace that functionality with their own code, meaning your app could create it's own Excel-compatible files. However, your users would still need Excel to use them.
You can also use other databases (eg., MySQL, Firebird, SQLite, and others) that are available that wouldn't necessarily cost your client anything if they installed it (or, for some, if you included it in your installation for them).
I will need a Sharepoint Server 2010 install for learning purposes.. I already have a Win 7 x64 os installation with vs2010 and I use it for my current development needs.
The question is ... would you recommend to install sharepoint onto an existing win 7 installation, create a separate OS instance (win7 or win 2008 r2?) for sharepoint development purposes or maybe create a VM for that? I have 4GBs of ram and I wont be able to extend it.
What are your experiences with dev environments for sharepoint 2010? I remember that 2007 was a real resource hog - maybe there is a 'magical' switch that allows sharepoint 2010 related services to be turned off?
If you thought SharePoint 2007 is a resource hog, SharePoint 2010 is even worse. The full installation creates lots of Windows services and IIS application pools. Which makes it really hard to stop SharePoint since all those services start automatically.I agree with others that you should use the VM approach but I think you need Windows Server 2008 R2 to be able to create 64-bit VMs.
Here's a link to powershell scripts for stopping/starting SharePoint services: http://blogs.msdn.com/b/emberger/archive/2009/11/16/stop-and-go-with-sharepoint-2010-on-your-workstation.aspx
I personally always run it in a different instance - either a separate machine or a virtual machine. Sharepoint 2010 is massive, and changes your system with a magnitude not seen by any previous sharepoint version, in terms of databases, scheduled tasks, services...
You should install your SharePoint 2010 in Server2008 R2 if you can ,since then you can do a complete install and use domain account.The installation in win7 is a standalone install and only use system account.It does not match what is in production...
Or if you can, virtualize your SharePoint environment.You need to give at least 4gb ram to SharePoint VM otherwise it is running like a dog.