updating and downdating

[Neil]

I was wondering if anybody could shed some light on this scenario, maybe
there is white paper somewhere ?

I have a vb.net app that runs on a few machines storing data in a local
access db, but if they are connected to web I want them to be able to upload
there data and pull down any updates that they do. whats the best way of
going about this?

Thanks

Neil

 

[William Ryan eMVP]

Delete the access files and wipe their remains from the registry.

SQL Server and replication would lend itself really really well to this
scenario and the Publisher/Subscriber model is made JUST for this.

You can do it with Access, but it'll take some fancy footwork that I don't
think is worht it. Remember that DataSets are local 'databases' themselves
so you could just use Access on the server, load yoru datasets from it, and
periodically send the updates back and refresh them. On a scale of 1 to 10
it's probably a 3. but Access will corrupt, will have security problems and
will be doing a job it wasn't really intended to do.

I'll gladly walk you through either process, just let me know.

Cheers,

Bill

www.devbuzz.com
www.knowdotnet.com

 

[Cor Ligthert]

Hi Neil,

In all those scenario's is one thing always the problem.
What is the leader updater, when did he update and what with conflicts.

One of the scenario's is to make for every part of your data one access
database the leader which may update and the rest may not.

Another scenario is to use timestamps and tell that after the timestamp date
everybody may update, however what to do as 2 are parallel updating.

Keep in mind that this are no easy scenario's however before you start you
have to make te rules for updating.

The downloading to the access databases is than ofcourse a piece of cake.

Just my 2 eurocents

Cor