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

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.

Awesome, Would be possible to create a vodcast?

Thanks in advance

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

Hey, what about DeskCloud apps. Hence Desktop + Cloud

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?

@ 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

@ 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