We have a access database split to front-end and back-end. How to link the back-end to sharepoint so that everybody can access it with their front-end desktop client?
I have created Sharepoint lists by exporting the database to sharepoint. I have also tried to import the lists into desktop access, but when I update the original tables, I do not see the changes reflected in the imported lists, or the lists on sharepoint.
What am I doing wrong, and is this the correct way of doing it?
In a new access file you should select:
External Data -> More (Under Important & Link) -> SharePoint List
Then make sure you pick "Link to the data source by creating a linked table." Follow the steps in the wizard and the new tables should appear yellow or gold in your access objects viewer (left hand side of main access screen)
If your data is not updating in the linked tables, you may need to select Refresh (or Refresh All) on the Home tab to make sure you have the most current data.
Related
Only 3 of the 5 lists in my SharePoint Online Team site are visible in the "Add an existing list" dialog. If I try to add either of the other 2 using a SharePoint link (the URL to the list), I get the error:
"That link did not work because you either do not have access or it is unsupported."
Those two are lists that I exported directly from Access to SharePoint, the others I either created from scratch in SharePoint or based on an uploaded Excel file. I created and am the owner of the Team site. I tried exporting the linked table for one of the lists from Access to an Excel file, then created a new list based on the Excel file. I was able to add that list to a Teams tab! That is a workaround, but it will entail a lot of work to re-do or copy over all of my formatting and views from the other list. I tried to find any settings, permission or otherwise, on the list that would fix it, but I am stumped.
Is there a way to modify this list from Access so that it can be added to a Teams tab?
I have a report that uses a CSV file as a datasource. In Visual Studio, I can point it at the file on a share and it works. When I deploy it to the SSRS server though, it brings back an error:
The Microsoft Access database engine cannot open or write to the file 'forecast.csv'. It is already opened exclusively by another user, or you need permission to view and write its data.
Putting the file onto a share which has Everyone granted Full Control, it works. This is obviously not an acceptable security situation. I am using the following OLEDB connection string:
Provider=Microsoft.ACE.OLEDB.12.0;Data Source="\\server\share\Apps\Folder1\Folder2\DEV\SSRS\Report Foo";Mode=Read;Extended Properties="text;HDR=YES;FMT=CSVDelimited"
Of interest, another report that uses an xls file as data source works on a share that does not have Everyone Full Control access. I initially thought that it was a DFS issue but it is actually that the share needs Everyone to have Full Control. Setting the share to Full Control for the user doesn't work, it has to be Everyone
I have logged this as a bug with Microsoft
I would like to ask if email address in an MS Access DB can be imported into MS Outlook (preferably in contact groups defined in MS Access)? If so, how can this be done?
Thank you.
The preferred way to work with outlook items in Access, is through linked tables. Access can directly link to your outlook files.
Steps (Access 2016):
Go to External Data
Click New Data Source
Click form other sources
Choose Outlook folder
Choose Link the data source by creating a linked table
Choose the address book you want to link
Click Finish
You now have a linked outlook address book as a table. You can use normal action queries to insert into and update your address book.
To import a CSV of contacts into Outlook,
click File then Open & Export
click Import/Export and Import from another program or file
click Browse and locate your .csv file
You'll have the option to map custom fields -- in case you don't have them stored in a standard way (like this sample).
More:
Import contacts Excel→Outlook
Outlook & CSV's
Adding a contact with VBA
So I have a table on a sharepoint site that another party updates with new items (spreadsheet style)
I also (currently) have an excel sheet that has reviews of each item that is on said sharepoint site.
The trick is things are added and deleted from the sharepoint site and I need to be able to track what is added and what is deleted so I know what I need to review. Orginally I did this on excell but I had to realign the reviews when things were added or taken out of the sharepoint site (a lengthy process) so someone suggested access but I am having issues trying to find a good tutorial that answer how I could do this.
my thought was to create access database that imported the columns from the sharepoint site and that I could just append more collumns to the end of it to add in my review comments. Would this work?
ultimately I would like to have my reviews put up on another sharepoint site.
Sharepoint can send emails when things change.
If you want to know how to see sharepoint data in MsAccess you can see sharepoint-msaccess-synchronization:
i would like to distribute an access front end to some people and i want to make sure that they do not edit anything in it; however when i change the extension to ACCDR it makes all the forms and tables disappear. what settings do i have to change in order for them to be able to open forms but not view them in design view or make any changes to the forms?
The accdr extension puts your Access application into the "runtime" mode of Access, meaning the end user does not have the ability to see the built in navigation tools within Access. You would need to provide the navigation mechanism within the application yourself (for example, a startup form with links to the forms \ tables you want the users to be able to interact with).
The accdr extension hides objects from the user, but it does not prevent them from changing the file extension back to accdb and modifying your code \ objects.
To completely "lock down" the application you need to create an accde file instead. This prevents the user from being able to open a form in design view and make changes.
The following two links provide additional information about the file types and ways to deploy your application:
Intro to the Access 2007 file format
Deploy and Access 2007 Application