Couldn't find any research on it online. Would love some insight before I download.
I did find one link, but not sure if what's listed is something extra I need to purchase or something I already have.
https://technet.microsoft.com/en-us/library/ee748653.aspx
Yes, you most certainly can use Access 2010 with SharePoint 2013.
In fact the real issue is if your instance of SharePoint is running Access web services. This is a requirement to use Access web publishing. The basic version of SharePoint does not include Access Web services (and thus no web publishing).
However all the basic SharePoint versions allow you to migrate tables from Access to SharePoint. So you can migrate your tables to SharePoint, and Access as a front end can use the linked table on SharePoint. And thus Access 2010 will work with SP 2013 in this regards,
However, if your 2013 SharePoint does not have Access web services, you cannot use the Access web publishing feature.
Related
I have created .mdb (Access macro) for client but problem is that they are migrating to Office365 so access will no be longer available for them.
Can I run Access macro without MS Access? I have googled it, I found .MDE file can solve the problem, but I don't have idea about it. Is there any alternative option or .MDE file will be the solution?
I'm a beginner in Access please let me know if any suggestions are available.
Thanks in advance!
You can't.
But Access is indeed available through O365 - you just have to select and pay for the correct subscription.
Microsoft just recently changed the Office 365 subscriptions. Microsoft Access is now included in all of the subscription levels except the Business Essentials subscription.
If users of your Access application have no license for Microsoft Access they still can use the Microsoft Access Runtime. The Access runtime is available for download free of charge and can run Access Database Applications, but you cannot make any design changes in it.
Microsoft announced that SharePoint will no longer support Access web apps. I am trying to build a relational database, and allow users to view and update the database through SharePoint.
Since I can't use Access anymore, what are my alternatives?
If all you require is the ability to make updates to the tables that comprise your database, you can still use SharePoint lists to do that and use the desktop Access client to achieve a relational database.
In access 2013, there is an option to create a web app.
My organisation is looking to explore this to way to take existing Access Desktop based application to Web, so that users can remotely also add data and view reports.
From this MS Support link, I came to know that Company will need to purchase office 365 to use Access web app.
When I went to 0ffice 365 business plans there are 3 types. Which one should I purchase? to be able to create web apps.
Our company has domain and website hosted/purchased at GoDaddy. Will we need to change anything on domain? in GoDaddy? If yes, Please specify what or point to post where I can get this info.
What will be other things required to be able to create web apps? Will one user licence sufficient? Will users who use front-end of Web app need to purchase additional licences?
For those with same Question,
Found this post at MS Office Community helpful
That should be any of the Office 365 subscription plans:
SharePoint Online Service Description
After more indepth searching and help from link in above answer,
Office 365 Business Essential did the job.
The web app is completely different than the Desktop, SO will now need to learn fresh.
I have a Access 2003 and lower databases. The company i work for is currently using MS Office 2007 and Access 2003 instead of Access 2007 because of issues with library references. We're currently converting the Access 2003 databases to Access 2007, but some users are already being upgraded to MS Office 2013 and Access 2013.
I am aware that Access will only change library references when design changes are made in Access 2013 which is not something we want because it will cause issues for users still using Access 2007.
My question is what constitutes a design change? For example we have some forms who's labels change based on user selection, would that be considered a design change? We do not want Access 2013 users to inadvertently make design changes.
The only way to avoid users making inadvertent changes would be to either use the Runtime instead of a full version of Access on their machine or force the database to open in Runtime mode by changing the your front-end's database extension to accdr.
Now, if your aplication relies on the standard office references, you should be ok (for most of them) as Access will use the right one for the version you have.
Any any rate, the fact that you are worried about users making inadvertent modification seems to imply that your users are sharing a front-end, which is not the recommended way to deploy an Access application: the application should be split.
Database containing the shared tables of the application remain on a network share. The Front-end, containing the UI and business code, should be deployed on the local machine of each user. The front-end only contain links to the tables in the backend.
This is a safe multi-user design since only data is shared, not the UI state.
Now if you have that design, if would not matter too much if users made accidental updates since that would only be local to their machine.
In that configuration, you can also keep sharing a specific mdb database with various front-ends for Access 2003, 2007, 2013 being deployed for different users.
Deployment is the hard part since you want that to happen automatically when there is a new version of the front-end available. There are tools like Auto FE Updater that can help.
We're looking for an easy way to display Access reports on the web. These reports have been written and viewed internally for years. They are not simple tables, but more complex charts and graphs. But, now people outside the organization need to see them. All of the data is in access. And, except for reporting everything else is working fine.
We have a web server that has permissions to see the Access database. However, the Access database server cannot be the webserver itself. So, the question is how do we view these reports on the web? This excellent solution, which I reference in case it helps others, (https://web.archive.org/web/20211020135306/https://www.4guysfromrolla.com/webtech/042600-1.shtml) does not apply, as it requires you to be on a company intranet . (Although, it may be possible to implement the solution outside of an intranet, so many security holes would be opened up that the developer leading this project would surely be fired.) If possible, we also do not want a solution that expects every client to install code, for example, the access runtime.
Is there a tool that can read the
access reports when requested? OR
Is there a tool that can upload the
data from the Access database on a
periodic basis and based on the last
retrieved data - it can display the
report that was written in access?
Other solutions ...
Thanks!
print the reports to pdf and then copy the pdf files to the webserver
Options:
output to PDF.
output to Access snapshot format and force users to use the snapshot viewer.
wait for Access 2010 with Sharepoint 2010 and Access Services and you're home free (as long as you can rewrite your reports to be full web reports, i.e., not VBA and only using the capabilities of web reports in A2010).
We deliver an Access app (and reports therefore) over a Terminal Server as a WebApp.