> Dear Jack,
>
> The backend is in a LAN while the replica is in a laptop. I will look into
> the Direct Synchronization and DAO.Database Object.
>
> Thanks for your help.
>
> Rob
>
> "jacksonmacd" <jackMACmacdo0nald[ at ]telus.net> wrote in message
> news:ccb592t7d9jvh3nqfo8aop8rfapjf25s6q[ at ]4ax.com...
>> If your replicas are on a single LAN, say, for occasionally-connected
>> notebook computers, then you should be using Direct Synchronization.
>> In such case, you can declare a DAO.Database object from your
>> frontend, and use the .Synchronize method of the database object.
>>
>> On the other hand, if your replicas are remote, you should be using
>> Indirect synchronization, which is not exposed as a programmable
>> method by the DAO database object. However, Michael Kaplan's TSI
>> Synchronizer object *does* allow programmatic control of Indirect
>> synchronization. You can find it at www.trigeminal.com
>>
>>
>>
>> On Fri, 16 Jun 2006 18:57:33 +1000, "Robert"
>> <Robert[ at ]discussions.microsoft.com> wrote:
>>
>>> We have an Access Database that a replica has been created by a developer
>>> that has left.
>>>
>>> There is different front end connected to the backend that is replicated
>>> with each other. We would like to know would it be possible add some
>>> codes
>>> so that end user not necessary to close the front end, open the backend
>>> and
>>> run synchronize. Can it be done at the Front End ?
>>>
>>> We are using Access 2000.
>>>
>>> Thanks
>>>
>> --
>> jackmacMACdonald[ at ]telusTELUS.net
>> remove uppercase letters for true email
>>
http://www.geocities.com/jacksonmacd/ for info on MS Access security
>
>