Does anyone know how to set up the connection beetween Sharepoint server and MS Access?
The main idea is so to see all the changes of data manipulation with Access' database in Sharepoint. I've no found any solving of this issue so far.
You could build and publish an Access database to SharePoint, please refer to this aricle for more:
https://support.office.com/en-us/article/build-and-publish-an-access-database-to-sharepoint-e68bf007-410c-43b2-bf21-322ddbcf5411
Besides, this article would be helpful to you:
Import, link, or move data to SharePoint
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.
I am trying to link a sharepoint list to another using sql server database. The ideal would be for this is to a live link so that when data in the sharepoint list is updated, the data in the sql server database is also updated. The reason that I need to do this is that I have an ASP page which will query the SQL database and display the results on a web page.
Any guidance would be much appreciated
Thanks in advance
SidJ
PS : I have done this in access before using the External Data tab ->
More -> Sharepoint List and then following the steps in the wizard, so
I know it is possible. Just not sure how to recreate this using SQL
Server as the destination for the data.
You can go BCS (Business Connectivity Services) or build something custom using a connector like http://www.bendsoft.com/net-sharepoint-connector/
Here is a small guide on BCS http://zimmergren.net/technical/sp-2010-programmatically-work-with-external-lists-bcs-in-sharepoint-2010
Working on SQL Server Monitoring Product and want to add SSRS monitoring capabilities in this.
When i try to search on web description/details of Report server Database i.e. ReportServer${InstanceName} and ReportServer${InstanceName}TempDB
But there is no description/details found on it.
But rather i found on Microsoft Forum as
"writing queries against the SSRS DB is not supported and the schema, content, interpretation of the content is subject to change without notice." on This Link comment of Lukasz
I only concern is it true that Microsoft don't provide this Info.
Why Microsoft dont provide this info even though we are paying lot of amount for this product?
am i suppose to drill down each and every table in above both the DBs and apply my logic to find monitoring attributes?
If you know any other ways to get this details it will really helpful.
Thanks in Advance.
The best resource I know to get started with admin scripts that run against the ReportServer db can be found here: http://gallery.technet.microsoft.com/scriptcenter/42440a6b-c5b1-4acc-9632-d608d1c40a5c
With some tweaking, it could help you out.
I'm using the Access Developer Extensions to attempt to source control this access database in TFS, however, I'm not sure I am doing it right. I can add a .mdb to source control and create a database from that source control.
I'm probably making a stupid mistake, but I can't figure out how to close the database I created from source control and reopen it while it's still under source.
Does anyone know of any tips or guides on this? I've searched for help on Access Developer Extentsions but I haven't found much. Thanks in advance guys!
I think I found what I was doing wrong. My database automatically compacts on close, so when it tried to do this Access asked me if I wanted "to remove the compacted database from source control". I thought this meant it would just not store the .mdb file, but still keep the objects (like tables, vba, queries, forms, etc) under source. However, this appears to completely remove it... from MSDN:
"Changes to Microsoft Access Behavior
Using the Compact Database Command
In order to take a database that is under source code control and deliver it to a user, you need a way to cut the database's ties to source code control. When you compact a database that is under source code control, Microsoft Access 2000 prompts you to remove the database from source code control.
To remove the database from source code control, Microsoft Access simply removes the Visual SourceSafe properties from the Microsoft Access database and its objects."
http://msdn.microsoft.com/en-us/library/aa155494(v=office.10).aspx
When I said do not remove compacted database from source control, my database and it's objects stayed under source.
I've been requested to implement a means of reporting on add/update/deletes on files stored sharepoint (MOSS 2007). After a little bit of research I found out sharepoint has out of the box document auditing which I enabled a couple days ago. I ran the report today, but excel spreadsheet was not very easy to look at.
Also I'm not positive of this, but I believe only site collection administrators can generate thsi audit report, and I dont really want to give the people who want these reports that much permission.
I'm curious what are some alternatives or recommendations? Should I try and get this information off the sQL Server and display it in reporting services, or perhaps try and build a include it in a dashboard?
Thanks
If you have access to the SSRS instance for SharePoint, you can get the report file. You can then make a copy and edit for the report you would like. permissions are a separate issue that can be tackled however you desire, especially if you create a copy and store as a new report.