Distrubuted databases
Anthony Culligan
can cope with the following application;
I require a central database on a 'dataserver' machine into which pc's will
dial by modem. When a pc dials in it will subscribe to a subset of the
data on the server. This subset will be transmitted to the pc and held
locally on the pc. The pc may add to or amend the subscribed data and those
amendments will be transmitted back to the server and the server database
updated. When the server implements changes, those amendments
are transmitted immediately to any pc's subscribing to that data.
Data volumes are expected to be small. The number of pc's subscribing at
one time would be upto 16 to start with but might be a greater number in
the future.
--
Anthony Culligan
cosb...@cerf.net
I have implemented basically this same scenario with one of my clients using
Clipper. As changes or new records are created at the remote sites, small
update databases are created, and these are sent via modem to the central
server. At the present time, there are 33 remote sites on this system, and
it works pretty well. I plan several major revisions (including moving to
a C-based database library) in the near future to enhance the communications
and fault-resistance. If somebody has a better implementation, I'd like to
hear about it, but if not, this is a workable solution.
Feel free to Email me if you want to discuss this in more detail.
Carl Osborne III cosb...@cerf.net
Scott McIntosh
: Can anyone advise me whether there is a database (preferably cheap) which
I don't know what platform you are targeting - or what you consider
"inexpensive" - but Lotus Notes will easily do this for you. It would
also allow for a lot of expansion. Additionally it provides built in
security, logging of transactions, built in design tools, e-mail, etc.
Connections can be made by network, direct serial connection, modem, etc.
all on a peer basis.
Ciao,
Scott
: --
: Anthony Culligan