Hello UA,

I have a question that I am pondering and trying to get some ideas on the way forward......

I have a basic 2010 database that has been split into a FE and a BE. The database ran great on a local server but due to offsite connectivity issues the database cannot be ran from anywhere but the local facility where the server lives. I have moved a TEST access database that has both the source tables and the sources forms to SharePoint (to increase connectivity) and it has made a list for each of my tables and linked the tables in the database back to SharePoint. My question is relatively simple.

If I put the source tables back into the exisiting database essentially combining the BE and the FE again and then move the tables to SharePoint lists would the FE still be susceptible to corruption? How stable is data in the lists, is it also susceptible to corruption?

If this is not the best idea does anyone have any other suggestions? I thought about moving the BE tables to SharePointList and then using the linked table manager in the FE to point to the SharePoint lists. I am not sure if this could even be done.

Thanks in advance for any help!

~Kyle

Kyle

Something in your description ...

I may be reading too much into what you posted -- if so, feel free to disregard!

One interpretation of your description is that you have a single FE. Everyone's PC points to/uses that single FE.

If this describes your configuration, you can expect to experience considerable corrupti... oh wait, that's what you're describing!

The standard design for FE/BE is one copy of the FE ... on EACH user's PC, and a single copy of the BE on the LAN. If that's your design, ignore the above!

Hi Jeff,

Two PC's each with their own versions of the FE. However for each computer we have multiple windows logon profiles using the FE in the Shared Documents Folder. Hope that helps in describing the issue a little bit better. Thanks for your reply!

Kyle

Hi Kyle,


I don't know if any systems out there would be immune to data corruption. Corruption is caused by many factors. Some factors may be applicable only to Access, but others will be applicable to SharePoint too.



Yes, you can use the Linked Table Manager to connect Access to SharePoint Lists, or you could also do it directly from SharePoint too. The best approach would probably be to "publish" your database to SharePoint.

Just my 2 cents... (IMG:style_emoticons/default/2cents.gif)

Guys as always thanks for the replies. You both helped validate my approach and gave me some useful information. I believe I am going to use the Linked Table Manager and point to lists in SharePoint after I move the BE tables to SharePoint. Thanks for the useful info!

KR

Hi KR,

(IMG:style_emoticons/default/yw.gif)

Jeff and I are happy to help. Good luck with your project.