The Access Show: Developing Access 2010 Hybrid Apps with Dick Moffat

re: The Access Show: Developing Access 2010 Hybrid Apps with *** Moffat

Albert D. Kallal — Fri, 30 Jul 2010 20:55:02 GMT

@ Nick Perez wrote:

I prefer this hybrid method that allows the user to run it on their desktop, but I didn't see how you can specify that during deployment. Can you clarify this? =============== It not really a option during deployment, but accomplished simply by emailing or posting a link to the published applications. If you do a view all site content, for the site, then you get a link at the top that says something like: Design with Access

(Modify this web database …etc.) So, it not really a check box or deployment option, but simply after you published, you send users to that site. However, I don't also see any problem with you simply emailing or distributing a copy of the client application. So, simply open up the published application as above and save it (it will be named YouDatabaseName.accDW file extension). Note that new file extension. So, any changes made to the published application will thus be downloaded to anyone who has a copy of this file when they launch that application. This updating includes changes to individual objects such as VBA code in forms or reports. So, all changes will be pulled (distilled) down to any client application when they open it. Albert D. Kallal (Access MVP)

Edmonton, Alberta Canada

re: The Access Show: Developing Access 2010 Hybrid Apps with *** Moffat

Albert D. Kallal — Tue, 27 Jul 2010 18:54:53 GMT

@ Jack Stockton wrote:

Just thought of a problem with the hybrid app...all the data is copied locally, therefore it can be stolen. Anyone thought of a way to protect the data other than using something like BitLocker? ---- You can choose to turn off the local cache. This will cost in terms of performance, but if this is requirement, then this does improve this case by quite a bit. (also, my apologies if this post appears two times) Albert D. Kallal (Access MVP)

Edmonton, Alberta Canada

re: The Access Show: Developing Access 2010 Hybrid Apps with *** Moffat

Nick Perez — Sun, 25 Jul 2010 05:11:55 GMT

I just signed up for an account on accesshosting.com but the example they show on their website is for the db to run on a browser, I prefer this hybrid method that allows the user to run it on their desktop, but I didn't see how you can specify that during deployment. Can you clarify this?

re: The Access Show: Developing Access 2010 Hybrid Apps with *** Moffat

dvana — Sat, 24 Jul 2010 02:45:23 GMT

Hey, what about DeskCloud apps. Hence Desktop + Cloud

re: The Access Show: Developing Access 2010 Hybrid Apps with *** Moffat

Ryan McMinn — Fri, 23 Jul 2010 21:15:51 GMT

@Gilad We are working on a post all about permissions and security. Hopefully will be up in the next couple weeks.

re: The Access Show: Developing Access 2010 Hybrid Apps with *** Moffat

llin85 — Fri, 23 Jul 2010 19:20:12 GMT

Awesome, Would be possible to create a vodcast?

Thanks in advance

re: The Access Show: Developing Access 2010 Hybrid Apps with *** Moffat

Michael — Fri, 23 Jul 2010 16:54:47 GMT

Biggus, I misread one of your messages above re the vba password, I thought you were leaning towards web dbs over hybrid, and so my hybrid advocacy post. And now of course I realize you are the presenter in the Access Show! Another concern re hybrid app security might center around users that have rights to run the app but not to view or modify all of the app's data. If all of the app's sharepoint data is pulled to the client, then a foxy user could probably gain access to all of the apps data outside of the designated user interface. Some data might be accessible (salaries etc) that might otherwise be off limits. As far as I understand it, such a user would have rights to the Access file in their my docs; would be able to get to the tables, code etc; just not push design mods back to the server. I think they'd be able to push data mods made outside the designated user interface back to the server. I'm not sure of this, have not tested/hacked; maybe I'm wrong. I'd say that the current Access Services hybrid app may not be quite as robust in this regard as it might be. Or maybe there is a way to get it all really locked down? Use the right tool for the job...there are many circumstances where a hybrid app fits perfectly. I think Microsoft did a great job on this, especially considering this is a first version.

re: The Access Show: Developing Access 2010 Hybrid Apps with *** Moffat

Biggus Dickus — Fri, 23 Jul 2010 13:20:33 GMT

Michael: A "Web" app can only interct with objects and data that is on the SharePoint Access Services Site. There is no interaction with local or other network resources. This may seem like a nuisance, but it can be worked around by having an application that's actually part Web-Only objects and part "Hybrid" ones that manage the data being fed to and from the Access Services Site as necessary from and Admin app. ***

re: The Access Show: Developing Access 2010 Hybrid Apps with *** Moffat

Biggus Dickus — Fri, 23 Jul 2010 13:15:39 GMT

Jack Stockton wrote: "Just thought of a problem with the hybrid app...all the data is copied locally, therefore it can be stolen. Anyone thought of a way to protect the data other than using something like BitLocker?" Not likely. Since the data requires the user's login be assigned some kind of rights on the SharePoint site to even get at the data on the client machine and since the temp file exists INSIDE the user's "Personal" Documents folder the chances of someone getting in without them knowing it is significantly small. Yes, if they copied the data and gave it to someone that wouldn't be nice, but the same is true of any app which allows you to print reports or extract to Excel anyway.... it's the human that is the risk not the software :-). That's an HR issue ratherthan a technical one IMHO. Yes probably some genius could eventually hack into their folders (or an admin which shouldn't be an issue anyway) but IMHO this is more than tight-enough security for 99% of needs. If that's still not enough then you should be using a SQL Backend or something like that anyway. But those other risks I alluded to earlier will still apply. But SQL Backends (as we said in the video) can still be an Access Services "Story" as well. ***

re: The Access Show: Developing Access 2010 Hybrid Apps with *** Moffat

Jem — Thu, 22 Jul 2010 17:21:06 GMT

Hello guys, I'd call this Pac-App (Package-Application). Seeing how things are being 'packaged' and send off/read from SharePoint 2010 servers. :) Same with the updates, where new information are 'packaged' nicely and delivered upon online connection between SharePoint server and Access application. No, I don't work for any delivery company, I just thought of receiving 'presents' in packages, while viewing this video presentation. And it is a good warm-fuzzy feeling to receive gifts. :) Thanks!