• Status: Solved
  • Priority: Medium
  • Security: Public
  • Views: 278
  • Last Modified:

Should I distribute copies of an Access .accdb for better performance or is a shared version OK?

Hello Experts,
I have an Access Databse that I have split and use a hyperlink on our sharepoint site that users use for the Front-end.  If everyone is using the same frontend file, does that slow down the application?  Should I destribute copies of the Front-end?  If that is the case should I post the front end on sharepoit (I think maybe then a local copy will be made on the users workstation)?

Thanks
terry
0
future_hooves
Asked:
future_hooves
  • 5
2 Solutions
 
wiswalldCommented:
Don't work with sharepoint but distributing the front end to all users should be your best bet.
0
 
Scott McDaniel (Microsoft Access MVP - EE MVE )Infotrakker SoftwareCommented:
Yes, you should distribute a copy to each user. Sharepoint is also a HUGE factor in this as well - I've yet to see a non-trivial application work well on Sharepoint. Sharepoint is great for sharing Word or Excel files, but IMO is not ready for prime time in regards to relational data. Sharepoint uses a SQL Server to store the data in "lists", and then uses XML to map those lists back to relational data ... this causes a LOT of roundtrips to the sharepoint server, which mean very poor performance. And, once you get more than about 2000 items in a table you can expect performance to really get bad.

If you really must share data on a server, then move to SQL Server and link your tables ... this is much better than using Sharepoint, IMO.
0
 
future_hoovesAuthor Commented:
wiswalld
Thanks for the response..... I had a feeling i should distribute
0
What does it mean to be "Always On"?

Is your cloud always on? With an Always On cloud you won't have to worry about downtime for maintenance or software application code updates, ensuring that your bottom line isn't affected.

 
future_hoovesAuthor Commented:
LSMConsulting,
"this causes a LOT of roundtrips to the sharepoint server, which mean very poor performance. And, once you get more than about 2000 items in a table you can expect performance to really get bad."
I think I am experiencing this now.  I have a list that, as of now, has reached 5739 items and the performance has really deteriorated.  Should I consider migrating this list directly to SQL server and use Access as a front end?

Thanks
Terry
0
 
future_hoovesAuthor Commented:
LSMConsulting,
I know this is straying a bit from the topic.... but If I am currently querying both Access tables and Sharepoint tables in the same Access Database,  Does the "Slowdown with a large sharepoint table" apply?

Thanks,

Terry
0
 
future_hoovesAuthor Commented:
Thanks for your help,

Terry
0
 
future_hoovesAuthor Commented:
Hi LSMConsulting,
I have continued this discussion here
http://www.experts-exchange.com/OS/Microsoft_Operating_Systems/Server/MS-SharePoint/Q_23914671.html

"I know this is straying a bit from the topic.... but If I am currently querying both Access tables and Sharepoint tables in the same Access Database,  Does the "Slowdown with a large sharepoint table" apply?"
0

Featured Post

[Webinar On Demand] Database Backup and Recovery

Does your company store data on premises, off site, in the cloud, or a combination of these? If you answered “yes”, you need a data backup recovery plan that fits each and every platform. Watch now as as Percona teaches us how to build agile data backup recovery plan.

  • 5
Tackle projects and never again get stuck behind a technical roadblock.
Join Now