From Newsgroup: comp.databases.ms-sqlserv

On Wednesday, June 10, 2020 at 4:06:58 PM UTC-7, Albert Kallal (Access MVP) wrote:

Remote desktop hands down is a better choice.

Migration of access tables to SharePoint is a "possible" solution, but not really a "general" solution for any old existing Access application.

Access 2003 - maybe 2-5% of applications would work with SharePoint

Access 2007 - much better - perhaps 20%, maybe 30% of applications could work with SharePoint - but we had no relational features.

Access 2010 - 60-75% of applications could now use SharePoint.

So it not every application is magic going to be able to work, but you have to learn by experience what works with this setup, and what will not rCo so as noted, you want to do some basic and preliminary testing here.

If you NOT using your own hosted SharePoint? Then your intitial table sizes really have to start out with 5,000 rows or less. They can grow to say 15,000 rows, but there are throttles and limits imposed.

If you have your own SharePoint server, then these "limits" can be removed, and you an push things to say 40,000 rows.

Given a choice between remote desktop, and that of SharePoint? In most cases it is a no brain choice - remote desktop is the way to go.

So, can you use SharePoint tables and migrate the access back end part to SharePoint? yes, you can, but how well this setup works will VERY much depend on how well the application is going to play with SharePoint. Not all applications will work well - so you would have to "test" and see if your existing application can work well. For those applications that "can" work well with SharePoint? Then it is a great low cost choice.

But, with remote desktop you as an general rule don't have performance limitations, and quite much any working access application can work with remote desktop. Not so with SharePoint.

Regards,
Albert D. Kallal (Access MVP 2003-2017)
Edmonton, Alberta Canada

Albert, my brother works for Nestle. He says with Sharepoint they use Excel on it as it can be used by multiple people on the same sheet. So Access is not used as much as they can do what they need with Excel. Is that an option to consider? I ask from ignorance as I've never seen Sharepoint in action.
--- Synchronet 3.21d-Linux NewsLink 1.2

From Newsgroup: comp.databases.ms-sqlserv

Thank you Albert for a very good explanation.
It would appear that the systems people are backing off the idea of transferring Access to SharePoint although they may use it for other activities.
I was being a bit concerned. If they change their minds again your comments will be most useful
Jim
On Thursday, 11 June 2020 00:06:58 UTC+1, Albert Kallal (Access MVP) wrote:

Remote desktop hands down is a better choice.

Migration of access tables to SharePoint is a "possible" solution, but not really a "general" solution for any old existing Access application.

Access 2003 - maybe 2-5% of applications would work with SharePoint

Access 2007 - much better - perhaps 20%, maybe 30% of applications could work with SharePoint - but we had no relational features.

Access 2010 - 60-75% of applications could now use SharePoint.

So it not every application is magic going to be able to work, but you have to learn by experience what works with this setup, and what will not rCo so as noted, you want to do some basic and preliminary testing here.

If you NOT using your own hosted SharePoint? Then your intitial table sizes really have to start out with 5,000 rows or less. They can grow to say 15,000 rows, but there are throttles and limits imposed.

If you have your own SharePoint server, then these "limits" can be removed, and you an push things to say 40,000 rows.

Given a choice between remote desktop, and that of SharePoint? In most cases it is a no brain choice - remote desktop is the way to go.

So, can you use SharePoint tables and migrate the access back end part to SharePoint? yes, you can, but how well this setup works will VERY much depend on how well the application is going to play with SharePoint. Not all applications will work well - so you would have to "test" and see if your existing application can work well. For those applications that "can" work well with SharePoint? Then it is a great low cost choice.

But, with remote desktop you as an general rule don't have performance limitations, and quite much any working access application can work with remote desktop. Not so with SharePoint.

Regards,
Albert D. Kallal (Access MVP 2003-2017)
Edmonton, Alberta Canada

--- Synchronet 3.21d-Linux NewsLink 1.2