Re: TSI keeps database locked after an indirect sync
- From: "David W. Fenton" <XXXusenet@xxxxxxxxxxxxxxxxxxx>
- Date: Wed, 24 May 2006 14:41:09 -0500
"Khurram" <kfhassan@xxxxxxxxx> wrote in
news:1148472719.593432.224860@xxxxxxxxxxxxxxxxxxxxxxxxxxxx:
I have access 2003 databases and have developed a little front end
in .net to synchronize the databases. I have not used replman at
all as we dont have it. I am using TSI synchronizer for syncs
databases between 2 offices over a telephone line. The indirect
sync works fine, but after the sync, the .ldb remains on the
computer which initiated the sync. Trying to manually delete the
file gives an access denied error. Only when the .net application
is closed down can I delete the .ldb file. This problem is similar
to that described in an earlier post in this newsgroup (see
http://groups.google.com/group/microsoft.public.access.replication/
browse_frm/thread/e8af9eb5c3109eb5/ba5bbd9dff95cead?lnk=st&q=tsi+cl
ose+database&rnum=3#ba5bbd9dff95cead).
Is the synchronizer still running at the time the LDB file is still
there? If so, shut it down and see if the LDB file goes away at that
point.
--
David W. Fenton http://www.dfenton.com/
usenet at dfenton dot com http://www.dfenton.com/DFA/
.
- Follow-Ups:
- Re: TSI keeps database locked after an indirect sync
- From: Khurram
- Re: TSI keeps database locked after an indirect sync
- References:
- TSI keeps database locked after an indirect sync
- From: Khurram
- TSI keeps database locked after an indirect sync
- Prev by Date: Re: Synchronization History AWOL
- Next by Date: Splitting a Replicated DB
- Previous by thread: TSI keeps database locked after an indirect sync
- Next by thread: Re: TSI keeps database locked after an indirect sync
- Index(es):
Relevant Pages
|