UtterAccess.com
X   Site Message
(Message will auto close in 2 seconds)

Welcome to UtterAccess! Please ( Login   or   Register )

Custom Search
2 Pages V < 1 2  (Go to first unread post)
   Reply to this topicStart new topic
> Move Access 2016 Database To Sharepoint 365, SharePoint 2013    
 
   
RobKoelmans
post Apr 9 2019, 07:43 AM
Post#21



Posts: 489
Joined: 25-November 14
From: Groningen, Netherlands


George,
Yes, Azure BE is a much better way to go but still not 3-tier. If you have subscribed to Office365, you probably have Flow. The funny thing is, that not only the architecture with Flow is better, it's also way faster if you throw a script at SQL-server and get back the result in JSON in ExecQuery in Flow (not using GetRows a.t.l.). By parsing a session key along with a One Time Pass Token on each round trip you can even make Flow session-aware by creating a record in a session table in SQL-Server and reinstall the session state on each roundtrip. Still, Flow will have one cycle because everything is done in the query script that Flow threw at SQL-server. This may seem complex but is in practice much, much more simple than any other solution for a number of reasons.
Rob.
Go to the top of the page
 
2 Pages V < 1 2


Custom Search


RSSSearch   Top   Lo-Fi    18th October 2019 - 11:30 PM