[AccessD] Access for Office 365 - New Linked Table Manager

[Jim Lawrence]

I think your concerns are very valid. 

I must admit I have equal fear that trying to run a serious business solely online is dangerous. A good backup, just like a data backup is priceless. When I was in the business and through friends that are still on the frontline, I found the a company's website could be run internally as an extended intranet as easily as it could be run via the internet. In fact, errors were discovered more quickly and upgrades were faster....the usefulness of many eyes can't be over stated.

I personally believe that being too attached to proprietary software, when there is no private ownership of it and especially when it is not stable, is very risky.
 
Jim 

----- Original Message -----
From: "Darryl Collins" <darryl at whittleconsulting.com.au>
To: "Access Developers discussion and problem solving" <accessd at databaseadvisors.com>
Sent: Friday, October 26, 2018 11:49:09 PM
Subject: Re: [AccessD] Access for Office 365 - New Linked Table Manager

I suspect the days of CD / perpetual licenses are limited.  It is likely MS will only offer a subscription based offering for their Office products moving forward.  Especially as office is distributed more extensively on alternate OS's and platforms to the tradition Windows / PC.

Cheers
Darryl.



-----Original Message-----
From: AccessD <accessd-bounces at databaseadvisors.com> On Behalf Of Borge Hansen
Sent: Saturday, 27 October 2018 1:07 PM
To: Access Developers discussion and problem solving <accessd at databaseadvisors.com>
Subject: [AccessD] Access for Office 365 - New Linked Table Manager

Further to Jim's mention about the new linked table manager - only available in Access for Office 365 - NOT in Access 2019 ...

I wonder if there will be ever be a perpetual licensed Access 2022 ??
If so, it would have the "new" linked table manager.
Ah, just missed it for inclusion in Access 2019!

https://support.office.com/en-us/article/manage-linked-tables-1d9346d6-953d-4f85-a9ce-4caec2262797

This is how we spare the User for battling with linked table managers - in fact they don't know about much of this stuff:

We are using DSN-less SQL-backend table linking using VBA in connection with a local lookup table with the names of all the SQL Db tables to be linked; plus  a local .accdb that the main .accdb app is linking to on start up to get the connection parameters to the SQL Db. This way, when we deploy new app versions to the client we don't have to worry about changing the connection parameters within the main .accdb app.
A small separate SQL db keeps tab on the latest version of the .accdb apps that we have deployed.
When deploying new app version to a master folder for users to get their new version from, we give the app a new version number and date in the 'version' SQL db and also reflect this new version number and date in a local table in the .accdb app.
When user starts up their app it will compare the app's local version number and date against the Version SQL db - When there is a newer version as per the 'Version" SQL db, User will be informed during startup of app and asked to run a separate update using a shortcut on their desktop to a small update .accdb app; and the main app will close down.
User then starts the small update .accdb that will pull the latest .accdb app from the master folder down to their local .accdb app folder....
As Users often keep their .accdb app open for any length of time it can be a hassle to push new app version to their local app folder... with this pull setup we avoid that...


/borge
--
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