[AccessD] "Faked" replication

Francisco H Tapia my.lists at verizon.net
Thu Dec 18 13:39:33 CST 2003


Seven,
   We are going to begin working on our own home brewed version of replication for our application.  It will basically be a spin off the microsoft termenology of indirect synchronization.
http://support.microsoft.com/default.aspx?scid=%2Fsupport%2Faccess%2Fcontent%2Frepl%2Freplinov.asp

First of all I think the GUID apporach is the correct one.  As far as comparing the value of the GUID that has been a "non" issue for us, as we dont' compare values, but simply look up the PKID for updating purposes etc.  I don't know about the IIS issues, or its reliability, but instead of us having FTP drop boxes we will be doing something a bit diffrent.  We are going to distribute our application using Sql Server 2000's MSDE.  I'm not looking at my notes but the process basically involves the following:

all records have a timestamp.
a master central db will keep the last update date
a client db is backed up with a guid filename, the databases is xfered  the central site and imported to an import db.

the exact reversal is done for sending data down but all guid.db's are sent to one central ftp site. 




-- 
-Francisco


Steven W. Erbach wrote:

>Mark and everybody,
>
>I appreciate the discussion this has generated, I really do. I've come to the conclusion that no-one on earth had tried FTP drop boxes for Indirect Synchronization...but I couldn't get a definitive answer!
>
>Mark, standard Microsoft replication doesn't appear to be an option any longer UNLESS I can persuade my client that his far-flung employees come back to the home office periodically to synchronize their database copies with the master. I don't think he'll go for that. Telling him that he needs an IIS Server on-site to accomplish Indirect/Internet Synchronization is shaky for two reasons: 1) he won't want to pay for it, and 2) I've seen lots of comments to the effect that it isn't reliable and isn't to be trusted.
>
>That blank record idea looked crazy enough to work at first...but it still doesn't address the fact that these laptops aren't connected to a network and my client doesn't have an IIS server.
>
>Arthur Fuller came up with a couple of fine acronyms for the situation in which I find myself:
>
>TWPWNRIS: Time-Wasting Problem With No Revenue In Sight
>IIDSTQIT: If I Don't Solve This Quickly I'm Toast
> 
>Regards,
> 
>Steve Erbach
>  
>


More information about the AccessD mailing list