I have now run this new Access Services application BOTH using a Terminal Services Session AND from my Native machine here in the Great Whote North connected using a VPN to the SharePoint Server in Seattle and the performance is exactly the same !!
Of course this is what you would expect considering that both are running with local caches and synchronizing with the SharePoint – Access Service Home site as necessary. I can change records on either copy and see the results on the other. But I now have actually SEEN it happen. I guess I’m from Missouri – you gotta “Show Me”.
This is HUGE IMHO, stuff because it allows people me to create Access applications that can be used Worldwide by corporations with distributed Offices. Of course this is not for those million record databases. but I personally can imagine millions of potential Departmental or Group applications that could benefit from this immediately. Who doesn’t know of an Access application that is starting to Wheeeze because it is being run using an MDB or ACCDW bacjend store across a WAN or even a LAN or that hasn’t been built because of that limitation ??
I believe this is a BIG deal and can’t wait to see SOMEBODY start to promote this to the world once the product ships…