Les You could always suggest some separation of the 'common' info for each client office, and create additional and separate Melbourne-only and Singapore-only tables.
Over years, I've done a lot of migration of databases / info systems to and from Access. Often, the clients wanted to keep Access front-end (but really didn't care if it was SQL Server at the 'back', and didn't know whether the data they 'saw' was in one or several tables). There are many ways to do this, depending on the foibles / vagaries / peculiarities of your clients' environment. I wasn't advocating that you just put an Access back-end database file or two (MDB) up in the sky. It would be sensible to convert the data to SQL Server format and host the data up there, though. What I was suggesting, as you probably deduced, was to use a common location in the first instance. As you probably realise too, Microsoft has some quite affordable Azure accounts for micro and small businesses. In short-speak, "SQL Azure". Just as a recent example article and step-by-step instructions, with some reasonable links to further explanations at the Microsoft Access Team Blog and to Azure pricing, try this - "Microsoft Access and Cloud Computing with SQL Azure Databases (Linking to SQL Server Tables in the Cloud)" http://www.fmsinc.com/microsoftaccess/cloud/link-to-azure-sql-database.html This does NOT require you to invest in any of FMS products. Of course, it would always be open to you to rewrite the front end in .NET at some stage - essentially keeping it as a desktop application. We're not talking any great sophistication in architecture or technology here. There are of course a growing number of people offering SaaS hanging off Azure, like Informatica Cloud's "Access Integration" product - http://www.informaticacloud.com/products/cloud-integration-processes/ms-acce ss-integration.html That gives synchronization, replication, backup, etc etc ... at a price. Now, your client wouldn't want to pay for that, I'm guessing! ________________________________ Ian Thomas Victoria Park, Western Australia -----Original Message----- From: ozdotnet-boun...@ozdotnet.com [mailto:ozdotnet-boun...@ozdotnet.com] On Behalf Of Les Hughes Sent: Tuesday, 7 September 2010 11:36 AM To: ozDotNet Subject: Re: Access Database Replication Ian Thomas wrote: > What are the problems of putting the MDB back-end in the cloud (using the > term loosely)? Surely both ends have a permanent always-on internet > connection? > I think there is some data they don't want shared between the offices? No idea really. This is one of those scenarios where I am asked questions on a 'need to know' basis, so instead of been given the bigger picture and a set of conditions in which to form a solution, all I get is a "we can't do that".... Grrrrr :/ -- Les Hughes l...@datarev.com.au
