UtterAccess.com
X   Site Message
(Message will auto close in 2 seconds)

Welcome to UtterAccess! Please ( Login   or   Register )

Custom Search
 
   Reply to this topicStart new topic
> Access Be On Sharepoint, Access 2010    
 
   
Brepea
post Jul 17 2017, 04:57 AM
Post#1



Posts: 364
Joined: 11-January 09
From: UK


Hi All - i have a request to go from Company's network folder structure to a SharePoint folder structure (in respect to data access to Access BE).

Currently, users have BE on a shared server location and FE on user's local c:drive (standard robust setup). I've not worked with SharePoint as the BE and wondering whether this is something people have done - is it possible/reliable? Their main reason for the change is that they don't want the process of "new users" to take days/weeks (because a work request via IT department for user to be setup on company folder takes so long)...

Thanks
Go to the top of the page
 
BuzyG
post Jul 17 2017, 06:53 AM
Post#2



Posts: 293
Joined: 20-September 12
From: Cornwall UK


Our company have a similar pollicy. I have found it all but impossible to set up a split access 2010 db on sharepoint 2010. Even if you create the BE, it appears you can not alter it, so need to create a new BE, if you wish to make any changes. Newer versions may differ.

You can link to share point list, easily but you can not set up cascade relationships between tables, so would need to handle every thing in VBA, which is erksome and very likely going to fail, and lose you data, at some point.

We have recently moved to Sharepoinr 2013, so I will revisit this subject I see if things have improved.

Will be watching this thread and hoping some one else has had more success it this area.


--------------------
Live to Surf
Go to the top of the page
 
GroverParkGeorge
post Jul 17 2017, 07:47 AM
Post#3


UA Admin
Posts: 29,955
Joined: 20-June 02
From: Newcastle, WA


Please do NOT try to run an Access BE from a SharePoint Library.

I understand that it could be done, although I've never heard of a successful installation.

If your organization insists on putting the data on SharePoint (and there are some good reasons to do that), you can export the tables from Access to SharePoint.

Beginning with version 2010, you CAN create and management Referential Integrity between SharePoint lists using the Lookup field mechanism. To do so properly requires a good understanding of RI and how it needs to work, of course. As with any local Access table relationships, the lookup field must store the related records' Primary Key as the Foreign Key, and not the value field. Other than that, it's a pretty good approach.

Performance should be okay. The amount of data you can store, of course, is a limiting factor, so be sure your requirements there are not excessive. I would imagine tables with up to 50,000 records would be reasonable.
This post has been edited by GroverParkGeorge: Jul 17 2017, 09:32 AM

--------------------
Go to the top of the page
 
Brepea
post Jul 17 2017, 08:53 AM
Post#4



Posts: 364
Joined: 11-January 09
From: UK


Thanks Grover

Yes - i thought this was about using lists...

So the company's only reason is simply to improve the time it takes to add a new user; i.e. via sharepoint they can do this instantly, but via IT they have to wait something like 1 week before user is given shared folder permissions.

I think I will push back on this...i.e. use the more robust network folders and try improve communication with IT team...which should hopefully lead to expedited new users...
Go to the top of the page
 
Brepea
post Jul 24 2017, 03:37 AM
Post#5



Posts: 364
Joined: 11-January 09
From: UK


re: 50,000 records - is that correct? I thought SharePoint lists had a limit of 5,000 records per table...?
Go to the top of the page
 
GroverParkGeorge
post Jul 24 2017, 06:22 AM
Post#6


UA Admin
Posts: 29,955
Joined: 20-June 02
From: Newcastle, WA


No, it is substantially more than that. At least 40,000 to 50,000. However, performance is likely to fall off in that range.

You may be thinking of the ability to add or change indexes, which is limited to lists smaller than 5,000 records in a default installation. Once the indexes are in place, though, the number of records can go well beyond that.

--------------------
Go to the top of the page
 
Brepea
post Jul 24 2017, 08:15 AM
Post#7



Posts: 364
Joined: 11-January 09
From: UK


What would be the main reasons to use SharePoint over the standard network folders?
Go to the top of the page
 
GroverParkGeorge
post Jul 24 2017, 08:17 AM
Post#8


UA Admin
Posts: 29,955
Joined: 20-June 02
From: Newcastle, WA


None, that I can think of.

--------------------
Go to the top of the page
 
BuzyG
post Jul 24 2017, 10:20 AM
Post#9



Posts: 293
Joined: 20-September 12
From: Cornwall UK


As per the original post. Sharepoint once set up correctly allows user groups to control there own views, on the data held. So no need to ask IS to set up folder permissions the local office admin or manager can set them. Another huge advantage, we have found, is the ability to share data with other companies over the web. Sharepoint allows us to set up shared areas, where we store documents and as per my first statement, can control what others have access to. Very powerful in this respect.

Alas sharepoint lists are a very poor substitute for a relational database. One example we use where the table in the database is a sharepoint list, is our list of platforms. As we as a company can be confident that list will never be more than a few hundred and it's data that is shared accross many projects, it sits well on sharepoint.
This post has been edited by BuzyG: Jul 24 2017, 10:24 AM

--------------------
Live to Surf
Go to the top of the page
 
theDBguy
post Jul 24 2017, 10:40 AM
Post#10


Access Wiki and Forums Moderator
Posts: 70,270
Joined: 19-June 07
From: SunnySandyEggo


Hi,

Pardon me for jumping in but I do know one company (Johnson & Johnson) where they used SharePoint to host their Access BE for a multi-user FE. I'll have to gather the specifics but if I remember it correctly, they were happy with how it worked. It was just like a network share, in their case. I was surprised to find out about it as well. I had no idea SharePoint can be used or set up like that. But like I said, I don't remember all the specifics. All I know is that they were not using SharePoint Lists but actually had the BE in a Document Library, and the FE was able to connect to it using a network share.

Just my 2 cents...

--------------------
Just my 2 cents... "And if I claim to be a wise man, it surely means that I don't know" - Kansas
Microsoft Access MVP | Access Website | Access Blog | Email
Go to the top of the page
 


Custom Search
RSSSearch   Top   Lo-Fi    26th July 2017 - 03:32 AM