Question Splitting a database for shared use on SharePoint 2010

rc-alex

Registered User.
Local time
Yesterday, 20:25
Joined
Apr 29, 2011
Messages
106
Hello,

I am creating a database in Access 2010 for HR to store its records and information. This database will be loaded into SharePoint server 2010 with Enterprise features. I need several people to be able to open and write to the database simultaneously without any issues.

Does anyone have a good article that covers what I need to consider/do as far as "splitting" the database, write locks, etc?

I am not using the SharePoint Access services because the capabilities are limited. Just a regular database with multiple users.

Thanks,
Alex
 
Thanks Boyd,
that definately looks like what I need to do.

So, if I understand correctly, I should load the database to the SharePoint site, split it into back and front ends, and only publish the location to the front end?

To continue developing the rest of the database, I would open a local copy of the database file that resides on the SharePoint site?

Thanks,
Alex
 
I thought you said you were not going to use Sharepoint.

AFAIK, you do not use a split database with Sharepoint. A split database is for when you are not using Sharepoint as the back end.

The information I have giving you so far is for when the split database does not use Sharepoint in any way.
 
I won't be using SharePoint Access Services. The back end will reside on the SharePoint site so that all users have access to it. But it won't be integrated into the site. The file will just sit there, on the server. Is that an issue?

Thanks
 
The back end will reside on the SharePoint site so that all users have access to it.

Not sure I follow.

Are you publishing the back end to Sharepoint lists?

Did you create a Web database?

What I have been posting is not for a web database.

In a standard split database that is not a web database the back end has nothing to do with the Sharepoint site. The back end resides on the LAN in a Windows Share where the users had Read and Write permissions for the folder.
 
I want to publish the entire back end to a SharePoint document library. It would sit there on the server inside the document library. The users would have edit rights on the file.

It would not be a web database, but a standard database hosted on the SharePoint site instead of a Windows Share.

Is this a bad way of doing things?
 
For an Access front end to link to the back end,it will require LAN access to the back end. It will not use the Sharepoint site. You can not link to tables via http. Access in LAN based.

Have you tried placing a copy of the back end on the Sharepoint site? Can you relink the tables to the back end on the Sharepoint site?
 
Boyd,

I will have to give that a try. Right now nothing is on a LAN. the SharePoint site is accessed via HTTPS. Is there any other way to share the back end, aside from setting up a LAN?

I would use the Access Services built into SharePoint, but they don't allow for the Total/Group/Last in queries, so I don't think I'd be able to pull information like "most recent salary", etc.

Thanks,
Alex
 
Thanks. They want to use FTP, but I don't think that will work. Your article mentions using SQL and then being able to link the database over http. Does this also work for https (our SharePoint site), and are major modifications needed to convert the existing access DB to SQL?

Thanks.
 
Your article mentions using SQL and then being able to link the database over http. Does this also work for https (our SharePoint site), and are major modifications needed to convert the existing access DB to SQL?

Using SQL? Not sure I follow. most database use SQL.

My best guess is the by SQL ( SQL => Structure Query Language) you are not really referring to SQL but to Microsoft's SQL Server.

If you are referring to an SQL Server database engine then what I talking about in the article is going directly to theSQL Server and bypassing Sharepoint.

With Access 2010 you could create a Web Database (can't use an VBA code) that can be published to a Sharepoint site. All the tables get converted to Sharepoint lists.
 
Hi, I came across this thread because I am trying to solve this exact problem. I have a still fairly new and still small database that I want to provide a small front-end for users worldwide. I have tried to get it working using Access web services in Sharepoint and there are so many unsolvable errors with my queries and TempVar's that I can't make anywhere close to a functional application without keeping Access as a non-web database.

Sharepoint is the easiest method for employees to access company documents so I was hoping I would be able to do exactly what is being posited in this thread: host a hidden back-end and accessible front-end on the Sharepoint server, effectively simulating a network drive. Have you figured out whether this is possible?

Thanks for any help you can provide!

Kind Regards,
Robin
 

Users who are viewing this thread

Back
Top Bottom