[AccessD] New Approach

 Note that with 2010, data is stored in SharePoint lists, not SQL.

 Best practice for SharePoint is to not have a list exceed 5000 items.

 A2013 is running against Azure and is another ball game entirely.

Jim. 

-----Original Message-----
From: accessd-bounces at databaseadvisors.com
[mailto:accessd-bounces at databaseadvisors.com] On Behalf Of Gustav Brock
Sent: Tuesday, March 05, 2013 03:12 AM
To: 'Access Developers discussion and problem solving'
Subject: Re: [AccessD] New Approach

Hi Stuart

That is a very interesting reference. 
Everyone here (that included me) not familiar with Sharepoint - which is the
"database" running in Office 365 - should watch the video "Migrating Access
tables to Office 365" it's only 12 minutes.

http://www.youtube.com/playlist?list=PL27E956A1537FE1C5&feature=plcp

What's not mentioned is performance. But for smaller databases I guess it is
OK.

/gustav

-----Oprindelig meddelelse-----
Fra: accessd-bounces at databaseadvisors.com
[mailto:accessd-bounces at databaseadvisors.com] På vegne af Stuart McLachlan
Sendt: 4. marts 2013 22:24
Til: Access Developers discussion and problem solving
Emne: Re: [AccessD] New Approach

On 4 Mar 2013 at 10:56, Rusty Hammond wrote:

> I've read a little about Access 2007/2010 being able to run with 
> linked/cached tables to a Sharepoint site, and can run disconnected 
> from the network/internet,  then when reconnected to the network, the 
> tables will synch up with the Sharepoint database.
> 
> Has anyone else heard of this and are you using it?  How well does it 
> work?  I've heard it works really well but don't know what the 
> limitations are (if any).
> 
> Rusty


A recent post on LinkedIn's PMADN by Albert Kaplan:
<quote>
A configuration that is working well for me is to use Access 2010 with
office 365.

So you purchase one office 365 p1 (small business plan). Total cost = $6 per
month.

You then take your application. Assuming split, you place the back end
tables on office 365.

You then link your desktop front end to that application.

You are done.

The application will now automatic run off line. And when you get back to
any internet connection. You can sync. All data from all other users will
appear on your system, and any changes you made will appear for everyone
else.

The beauty of this setup?

You write and use Access - regular VBA etc.
You don't have to write or setup a bunch of sync code - it is automatic and
built into Access.

Even better?

If you have Access 2010, the whole thing can be setup in less time than it
took me to make this post.

No server has to be setup.
No learning + setup or install of SQL server.
No purchase of new software.
No writing of a whole bunch of sync software.

I explain in the following video how you upload related tables to SharePoint
or office 365:
http://www.youtube.com/playlist?list=PL27E956A1537FE1C5&feature=plcp

</quote> 


-- 
AccessD mailing list
AccessD at databaseadvisors.com
http://databaseadvisors.com/mailman/listinfo/accessd
Website: http://www.databaseadvisors.com