Dale, "Pro Access 2007" by Martin Reid has some useful information on this subject. As for a variation on your option 3, this may be applicable: http://www.thinsoftinc.com/product_thin_client_winconnect_server_xp.aspx -- Steve Schapel, Microsoft Access MVP Dale Fye wrote: I'm looking for a good reference on deploying Access 2007 database (data, forms, reports) in Sharepoint
On 22 jun, 03:17, Luis María Guayán <luisma...@portalfoxxx.com> wrote: Dicen enhttp://www.mydigitallife.info/2008/06/13/enable-multiple-concurrent-r... que se puede tener concurrentemente 3 usuarios de escritorio remoto en una PC con Windows XP (el usuario actual, mas otros dos) modificando una dll de Windows ¿Será cierto che? ;-) -- Luis María Guayán Tucumán, Argentina
The only reason to Replicate a database is if the users spend their time disconnected from it and cannot connect over the Internet. Assuming they can connect, if you want to spend a fair amount of money building a web front-end, but you can just use a Terminal Server, and keep the front-end, If you have only a dozen or so users, you might even consider WinConnect: http://www.thinsoftinc
Colin, As long as the volume of data is not huge, Anthos's idea of using Access 2007 with SharePoint may well be a good solution. You probably wouldn't need "SharePoint 2007" - the free Windows SharePoint Services 3.0 should do the trick. Another approach would be to use Terminal Services, so the users access and run the database remotely. Albert Kallal has some information at http
Consider using a VPN (virtual private network) instead of the internet. By using a Terminal Server, you can achieve faster speeds and use the database you've already built, without any modification. I just finishing setting up such a network for about 50 clients using a Microsoft Terminal Server: http://www.microsoft.com/windowsserver2003/technologies/terminalservices/default.mspx Only
