leicklda" < XXXX@XXXXX.COM > wrote in
news: XXXX@XXXXX.COM :
Temporary tables shouldn't be in the front end, but in a separate
temporary mdb linked to the front end. That will mean that your
front end won't bloat, and it might fix the issue.
I assume your front end is not replicated.
Are you not waiting until the synch finishes before allowing the
user to work in the app?
Sounds like an LDB file is not getting deleted. There are two
potential causes for this that I can think of:
1. users don't have appropriate permissions on the folder where the
database you're trying to change is located.
2. the database variable in your app that is used for the synch
isn't being de-initialized. You may want to try the two
possibilities for which replica you use for which. When you do this:
Set db = DBEngine.OpenDatabase("[local back end"]
db.Synchronizer "[remote back end"]
Set db = Nothing
It may be that there's an implicit lock on the remote db that is not
released when the code finishes running, so, instead, try it in the
Set db = DBEngine.OpenDatabase("[remoted back end"]
db.Synchronizer "[local back end"]
Set db = Nothing
That would mean you've explicitly closed and cleared the connection
to the remote back end.
Of course, if you're not closing your db variable and setting it to
Nothing, that could be the problem.
And if you're using JRO for your synch, I'd suggest you abandon it
and change to DAO, as above, since DAO is native to Jet and JRO is
just an add-on necessitated by MS's insistence on replacing DAO with
the non-native ADO, and MS now deprecates the use of ADO and its
ugly step-children (like JRO) in favor of DAO for use with Jet data.
Try switching the two.
Secondly, you really oughtn't be synching with the design master, in
any event. You should use the DM *only* for DESIGN, and not as your
end point for regular synchs. Doing that would remove the editing
problem entirely without having to experiment with code.
David W. Fenton http://www.dfenton.com/
usenet at dfenton dot com http://www.dfenton.com/DFA/