[AccessD] New Approach

Stuart McLachlan stuart at lexacorp.com.pg
Tue Mar 5 18:48:57 CST 2013


R.I.P. ?

:-)

On 5 Mar 2013 at 19:36, John W Colby wrote:

> ROTFL, my question exactly.
> 
> ;)
> 
> John W. Colby
> 
> Reality is what refuses to go away
> when you do not believe in it
> 
> On 3/5/2013 6:11 PM, jack drawbridge wrote:
> > Darryl,
> >
> > What exactly does all that mean in terms of Access?
> >
> > On Tue, Mar 5, 2013 at 6:01 PM, Darryl Collins <
> > darryl at whittleconsulting.com.au> wrote:
> >
> >> I have moved my Wife's small business IT ops to Office 365 and it has been
> >> brilliant.  Their database requirements were fairly modest and are now all
> >> handled by Sharepoint lists rather Access or a custom SQL Server set up.
> >>   Huge upside is all their IP is now on Sharepoint and can be access by any
> >> authorised user via any web browser on any device.  They also get a rock
> >> solid version of MS Exchange so they now have all their calendars online
> >> with visibility on when they are available or not etc - just like if you
> >> were working in a large corporate.
> >>
> >> All their client notes are now stored on Onenote and upload to the
> >> sharepoint site.  Again, this way the client notes can be access remotely
> >> and by any user which is great for them if the have to cover another
> >> therapist when she is sick or not available.
> >>
> >> Of course this is great for me as the maintenance on their IT systems is
> >> now minimal - MS update and support the software so that is way less work
> >> for me.  She pays a small monthly fee (about $6 per user) and you can add
> >> and remove users as required.   The only issue was the single Mac user
> >> (there is always one ;)) I ended up putting Windows 7 on Bootcamp for them
> >> as Office Mac doesn't support Onenote and Office 365 works a lot better
> >> with native Office 2010 (as you would imagine).
> >>
> >> Anyway - I am a huge fan.  Loving it. Saved gobs of time and lots of money
> >> using this approach.
> >>
> >> Your mileage may vary of course, but I think for many small businesses it
> >> is just brilliant.
> >>
> >> Cheers
> >> Darryl.
> >>
> >>
> >>
> >>
> >> -----Original Message-----
> >> From: accessd-bounces at databaseadvisors.com [mailto:
> >> accessd-bounces at databaseadvisors.com] On Behalf Of Gustav Brock
> >> Sent: Tuesday, 5 March 2013 7:12 PM
> >> 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
> >>
> >>
> >>
> >> --
> >> AccessD mailing list
> >> AccessD at databaseadvisors.com
> >> http://databaseadvisors.com/mailman/listinfo/accessd
> >> Website: http://www.databaseadvisors.com
> >>
> 
> -- 
> AccessD mailing list
> AccessD at databaseadvisors.com
> http://databaseadvisors.com/mailman/listinfo/accessd
> Website: http://www.databaseadvisors.com
> 





More information about the AccessD mailing list