G
Guest
I am developing an Access 2000 application to handle all the admin for an
international photographic competition. The process of registering all the
entries as they come in over a period of a month or so will be handled by
four or five volunteers using their own PCs at home.
For initial distribution, I am planning to use a combination of the Access
2000 Package & Deployment Wizard and WinZip software to create a
self-extracting MDE version of my application. This file will then be made
available for download on my website. This process has been tested and
appears to work fine.
I now need to find the best way to merge the data from each user at regular
intervals and then redistribute the merged tables back to the users (it would
not be a big problem if data entry had to be frozen during this merging
process). The data volumes are not enormous. There are about 6000 separate
entries each year from about 1000 entrants and we would want to retain data
in the live system for about 5 years. The only available methods of data
communication are via the Internet and email. I will probably split the
database into a front end and a back end.
Is replication a valid tool in such circumstances for the back end database?
I've seen comments suggesting that replication only works if the PCs are
interconnected via a high-bandwidth link such as a LAN. Is this correct?
If replication is not a suitable tool, what are the best ways to handle the
merging of 4 or 5 versions of about a dozen tables?
David
international photographic competition. The process of registering all the
entries as they come in over a period of a month or so will be handled by
four or five volunteers using their own PCs at home.
For initial distribution, I am planning to use a combination of the Access
2000 Package & Deployment Wizard and WinZip software to create a
self-extracting MDE version of my application. This file will then be made
available for download on my website. This process has been tested and
appears to work fine.
I now need to find the best way to merge the data from each user at regular
intervals and then redistribute the merged tables back to the users (it would
not be a big problem if data entry had to be frozen during this merging
process). The data volumes are not enormous. There are about 6000 separate
entries each year from about 1000 entrants and we would want to retain data
in the live system for about 5 years. The only available methods of data
communication are via the Internet and email. I will probably split the
database into a front end and a back end.
Is replication a valid tool in such circumstances for the back end database?
I've seen comments suggesting that replication only works if the PCs are
interconnected via a high-bandwidth link such as a LAN. Is this correct?
If replication is not a suitable tool, what are the best ways to handle the
merging of 4 or 5 versions of about a dozen tables?
David