[thelist] Synchronising databases + DB filesize

Atkins, Chris CAtkins at patriothomes.com
Thu May 25 12:16:05 2000


> Is there any way to synch databases, so that sales reps could dialup once
> a
> week, and have some kind of application determine rows modified in the
> last 7
> days, and update the local database? (The database would be Access.) If
> this was
> possible, I could arrange things so that the head always did his updates
> at a
> specific time (say Sunday night), and then the sales reps did their
> updating
> Monday morning before they began their week's wanderings.
> 
	[Atkins, Chris]  Yeah, in Access 97/2000 you can go to Tools>Create
Replica.
	Then, if the sales reps have Access on their laptop, you can make
the
	database replica available over the internet and they can use
Tools>Sychronize Now
	and it should give them the option of using a Replica on the
Internet.
	Look through the Access help files for more information, but the
reps will
	definately need a bit of instruction.  Caveat:  I've never done this
before, but
	it supposed to work. :)

	DAO also has a "Synchronize" method for Jet databases (like Access).
If
	you look up the help file for it you can read how it can be used to
Sync
	up two replicas.  You could write a little VB app for the reps to
run that
	would synch up the two databases for them, but that might be more
involved
	that what you were looking for.

	The problem with both of these methods is that a bunch of system
tables
	and replication info is added to your original database.
Fortunately it's schema
	remains intact so all of your scripting and such should work fine,
but it does
	make the database bigger (by how much I have no idea).

> Can anyone guess as to the filesize of an Access database (.mdb) which is
> primarily made-up of a product table with 2500 or so rows? The information
> stored per row would probably be a half page of text, and a few
> price/stock
> variables - nothing elaborate.
> 
	[Atkins, Chris]  Without knowing the datatypes it's not really
possible to
	give a decent guess, but it had better be smaller than 1GB, Access'
max.
	db filesize. :)

	Good luck!