Force Synchronize Funny

[Peter Harden]

The following details may be useful to anyone experiencing funnies in  
synchronizing local files with the server database.

--- THE PROBLEM ---

All my enterprise dbs have an .Initialize procedure that i)  
synchronizes the database on being opened; and ii) checks this  
synchronization.

Every now and again -- more often than I'd like -- the procedure  
fails at the verification phase: or rather the procedure doesn't fail  
but the verification fails.  If I then manually choose Wizards >  
Sharing > Verify Synchronization then this too fails with Missing  
Records reported.

If I then Force Synchronization to solve the problem, it just plain  
won't.  When I try to Verify Synchronization after a Forced  
Synchronization, the Missing Record(s) are still reported.

--- THE SOLUTION ---

The problem seems to stem from Enterprise losing track of how many  
records there actually are on the server.  Today I had a client with  
189 records, but on the server it said there were 190.  However, a  
"save as text" from the server database included only 189 records.   
There's no menu item for "selectall" in Enterprise, but you can get  
round this by creating a new file and writing a procedure to do so in  
that file (ie openfile "Problem database" selectall).  Having run the  
procedure, it changed the record count on the shared database from  
190 to 189. After that, synchronization and verification happened  
with no issues.

Peter Harden
===================================
Peter Harden
Harden's Ltd
14 Buckingham Street
London
WC2N 6DF

T: 020 7839 4763
F: 020 7839 7561
W: www.hardens.com
===================================
Registered in England & Wales, No 3930364
Reg. office: 14 Buckingham Street, London WC2N 6DF
===================================



-------------- next part --------------
An HTML attachment was scrubbed...
URL: http://provue.com/pipermail/qna/attachments/20080310/ade9fc52/attachment.html