1. publish accde - this isn't supported. You can restrict using permissions users ability to modify and create new objects. We have a blog post on this topic nearly done.
2. Client verses web objects. If you want to sue VBA--use client objects. You can mix client and web objects if it makes some sense for your app to have a web interface.
3. There aren't any hard limitations for frontend users. We test 600+ users regularly.
4. There is a throttle for limit of records in the list for data that is stored in SharePoint. I think it defaults to 500,000 but don't remember for user. I strongly recommend prototyping your app against real data sets with real queries to get a sense of
performance. It is nearly impossible to generalize perf characteristics because so much of it relies on the design of the app and types of queries you are using. We sort of think of most apps falling well under the 100,000 record range.
5. FE/BE for web apps. i would expect this to work fine.
6. SharePoint has a pretty robust model for security permissions on lists and items. You can do most anything outside of column level permissions. We don't make it easy to get to list and item level permissions but they are available if you work hard enough.
Permissions are always enforced when you sync back regardless of what you do while offline. For example, if you update a list offline that you don't have permissions--SharePoint will block the update.
7. You can do it wiht data macros. I have a blog post nearly done on the topic. Expect it in the next couple of days.
8. yes. TEst performance characteristics of the types of queries you expect to write before moving too far.
I will see if we can hook you up with accesshosting folks. Watch your email.
@ Ivan_ - Minimum version of SharePoint is likely going to be the Enterprise edition. You simply need the permission to create sites to publish and edit Access Services applications. If you can create a site--you should have the permissions to create apps.
Chris--it is really hard to give you advice about your particular app without understand a ton of other variables. There definitely are people that make a good living selling Access applications. Some examples include:
These customers have done really well with ribbons. I think all are very excited about the fresh new look it brought to their product.
We absolutely see small business as very important to our long term bet especially for hosted solutions where small business don't want to maintain servers. I would love to take this offline and talk with you more about our opportunities for partnering in
the small business space--my email address is c l i n t c ATSIGN m i c r o s o f t DOT c o m.
I'm not saying that Access is perfect for every ISV project--it simply isn't but there are some scenarios for ISV where it makes a lot of sense.