John W Colby
jwcolby at gmail.com
Mon Oct 14 12:02:28 CDT 2013
Rocky, If you are talking a literal Access BE, an MDB, then this is a known no-no. working with an Access BE over any slow WAN causes corruption issues. OTOH directly linking to a SQL Server BE works just fine, if a tad slow sometimes. Basically the link is an ODBC (little green world) and uses a driver which causes a "disconnected recordset" environment. It grabs the data from SQL Server and closes the connection. The user does whatever and then Access/JET opens a connection and updates SQL Server as needed. You pretty much MUST use a timestamp field in the table. Jet reads the timestamp field (which isn't actually a date / time) when you read the data from the table. It then checks that the timestamp has not changed when it is time to perform updates back to SQL Server. If the timestamp changes then Access informs the programmer / or user that "the original data has changed" kind of thing. You the programmer has to handle cases where the original data has changed. John W. Colby Reality is what refuses to go away when you do not believe in it On 10/14/2013 12:51 PM, Rocky Smolin wrote: > Dear Lists: > > Is anyone running an Access back end in the cloud with the front end local > to the desktop or laptop. It has come up twice recently. > > If so, what cloud service do you use? It would seem that the cloud server > would have to be mapped to a logical drive on the local box so you could > navigate to the back end to link up the tables, yes? > > MTIA > > Rocky Smolin > Beach Access Software > 858-259-4334 > www.bchacc.com <http://www.bchacc.com/> > www.e-z-mrp.com <http://www.e-z-mrp.com/> > Skype: rocky.smolin >