Kevin, Your plan looks pretty good to me (a bit this on details but.....) except step 3. The central site has NO clue what data is missing, other than perhaps a set of standard items that MUST be there. Better to let the remote site ALWAYS send changes to the main site. This will reduce the traffic overhead and will not require changes on server side when the data architecture changes.
This would work somewhat like a "change log" or "activity audit log". Best regards, Donald R. Donigan donigan technology, LLC dba Desert CODE Works [EMAIL PROTECTED] [EMAIL PROTECTED] -- No virus found in this outgoing message. Checked by AVG Anti-Virus. Version: 7.0.308 / Virus Database: 266.11.9 - Release Date: 5/12/2005 ------------------------------------------------------- This SF.Net email is sponsored by Oracle Space Sweepstakes Want to be the first software developer in space? Enter now for the Oracle Space Sweepstakes! http://ads.osdn.com/?ad_id=7393&alloc_id=16281&op=click _______________________________________________ Hardhats-members mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/hardhats-members
