visual studio 2013 windows application using ms access database - visual-studio-2013

I created a visual studio 2013 windows application(Information System), and i'm planning
to install in 5 computer machine and login their own user account.
My problem is... what is/are step/s to do for the 5 computer machine to access the single
access database?
Is there any technique aside from sharing the access database via LAN?
Is there someone here who could guide me? please...
emman

To answer the short question, just shared access to the database file itself.
Refer to the following MS articles that explains the concepts succinctly. The process is the same even if the front end is C#.
Office 2007: http://office.microsoft.com/en-us/access-help/ways-to-share-an-access-database-HA010279159.aspx
Office 2010: http://office.microsoft.com/en-001/access-help/ways-to-share-an-access-database-HA010342110.aspx
Office 2013: http://office.microsoft.com/en-001/access-help/ways-to-share-an-access-desktop-database-HA102749577.aspx
You are specifically interested in the database portion of 'splitting a database'

Related

VB 6 Data Access Component installation on Windows 2012 Server

I am trying to install Visual basic 6.0 on windows 2012 server, it’s not installing, and if I remove data access components it’s installed successfully. But I am not installed data access component excel reference is missing.
This was also my problem.
I solved it by unchecking the Data Access Components installation in Visual Studio 6 and, instead of that, by installing theAccessDatabaseEngine.exe which is the 32-bit version of Microsoft Access Database Engine 2010 Redistributable
Link to download here: Microsoft Access Database Engine 2010 Redistributable
From the MS Documentation:
The Office System Drivers are only supported under certain scenarios,
including:
Desktop applications which read from and write to various files formats including Microsoft Office Access, Microsoft Office Excel and
text files.
To transfer data between supported file formats and a database repository, such as SQL Server.
Important note: sadly, in my existing applications i had to change my MDAC references, and the connection strings like described below (for new applications this isn't an issue):
If you are an application developer using OLEDB, set the Provider
argument of the ConnectionString property to
“Microsoft.ACE.OLEDB.12.0”

Sharepoint 2013 Farm Visual Studio cannot connect

I have Visual Studio Ultimate 2013 and SharePoint Designer installed on my local machine. I have a SharePoint installed on a server farm that i have full read and write permissions on. My problem is when i try to create the project the wizard to connect to the SharePoint will not show up and it says i need it installed on my local machine. I have read many forums posts such as
https://social.msdn.microsoft.com/Forums/en-US/5853a07e-e033-43ab-929b-f5766354fea9/cannot-connect-to-sharepoint-2013-farm-with-office-tools-for-visual-studio-2012?forum=sharepointdevelopment
https://msdn.microsoft.com/en-us/library/office/jj220047(v=office.15).aspx
along with others these are just the ones still open in my browser. I would love some help or a proper tutorial because the ones i am finding are no help and im not seeing anything besides a error message saying i cannot create a project until i install foundation or server for sharepoint
This is a case where the error message means exactly what it says. You must install SharePoint on your development machine in order to use Visual Studio for local SharePoint development. You can develop on Windows Server 2008/2013 (most common solution I've seen), install SharePoint on your Windows 7/8 machine (which is painful to do but possible), or set up a remote environment for development after signing up for an Office 365 Developer Site.
After hours of searching I found a work around for anyone who is running into this problem... You need to make a web reference to the SharePoint site then you can access the XML and do it that way. Microsoft hides the option its under service reference then you click web reference add the URL and a easily called name add it and your good to go.

Upgrading TFS 2008 to TFS 2012

I am currently working on a TFS 2008 to 2012 upgrade. Here is my situation: my current TFS 2008 box is Server 2K3 with SQL Server 2005 backend. I am not entirely sure what my upgrade paths are but I think the following 2 scenarios are the most likely:
Migrate the databases from SQL 2005 to SQL 2012 and then point TFS 2008 at the new SQL Server. From there I can upgrade TFS 2008 to 2012.
Spin up a new Server 2008R2 box and do a clean install of TFS 2012 with a SQL Server 2012 backend.
The network guys would really like me to do option 2 because they want to decommission the Server 2003 box but my concern is how would I get all of the data in TFS 2008 over to the TFS 2012 instance? I have looked around the MSDN and Google but I haven't come across any documents that explain how to do this kind of upgrade.
Additionally are there any pitfalls that I should be on the look out for?
Any help would be greatly appreciated!
The Microsoft Documentation doesn't make this abundantly clear so for anyone in the future that is in a similar situation this is a great little how to. Some of the screens vary to what you actually see but it is mostly spot on.
Some points
If you spread your Data and Application Tier across multiple servers make sure the user account you specify for 'Report Reader Account' has access to both servers and has the 'Log on locally' permission.
Pitfall: After getting TFS 2012 configured I was getting a strange URL exception when VS2012 attempted to connect to the imported project collection but not when trying to connect to a project collection created from within 2012. A server bounce corrected this problem.
All and all the process is very straightforward and TFS2012 stands up pretty quickly.
There is great documentation on MSDN: http://msdn.microsoft.com/en-us/library/ms404860(v=vs.100).aspx

Can't Create or Save File to Network Share in Visual Studio

I'm not certain when this problem started occuring, but it was approximately a few weeks ago when I upgraded from Visual Studio 2008 to 2010. I am on Windows XP Professional. The share is on a server running Windows Server 2003. I have a solution which contains a web site (accessed via UNC path, network share) and some class projects that reside on my local workstation. When I open a file from the website, and try to alter and save the file, I get the following error:
" Cannot access this file. Check security privileges over the network drive."
I've checked privileges on the root folder and I do indeed have full control. Could anyone give me any insight as to what I could be missing?
Are you running Windows Vista or Windows 7 with User Account Control (UAC) enabled? If so, Visual Studio 2010 requires administrator permissions to do certain tasks, including IIS management and network share saving.
Try opening Visual Studio 2010 with the Run as Administrator command. Hope that solves your problem.
Turns out a sysadmin removed all permissions and user profiles from a chunk of servers and forgot to inform me. Thanks for the insight, all.

Web Access in Visual Studio 2010

I try to upgrade a plug-in that was on webaccess 2008. Whe were using WebAccessSession to get the user name of the current user logged (WebAccessSession.Current.Connection.UserName ). I Imagine now that it is in tfsConnection but I'm not sure.
Is there any documentation that tells what really changes between Team Foundation Server 2008 and Team Foundation Server 2010?
No documentaion that details things at the level that you are looking for I'm afraid. As far as I know, plugging in to Web Access is not supported via any specified API so any integration you have done yourself would be classed as unsupported so you'd be on your own when it comes to figuring those sorts of changes out. Sorry.
As far as your question about Web Access, this blog post from Hajan Eskci details what's happening with Web Access:
Team System Web Access in TFS 2010 Beta1
Until now, Team System Web Access was published as an out of band power tool. In this release and beyond, Web Access is now an integrated part of TFS, and it is installed by default when you install TFS.

Resources