-2

I am developing winform app that runs in two differen pc's

I want to create a replica and get the changes over the internet

  • How can i do that?
  • & how can I create replica and sync it using C#?

any ideas will be appreciated

sehe
  • 374,641
  • 47
  • 450
  • 633
marwa
  • 11
  • i think marwa thought about replication... – Renatas M. Aug 29 '11 at 10:37
  • Yes I mean replication,Can u help? – marwa Aug 29 '11 at 10:58
  • I don't understand why this question was closed. Jet Replication has a long and venerable history (though MS is phasing it out in favor of Sharepoint), and can work very well in certain scenarios. I wouldn't recommend it for an Internet situation, as it means using Indirect or Internet replication, which very quickly get complicated (and are subject to failure because of external dependencies). My Jet Replication Wiki has lots of resources: http://dfenton.com/DFA/Replication/ – David-W-Fenton Aug 30 '11 at 21:49
  • From the link to 'Jet Replication': _'[This is a despicable approach for Microsoft to use, and convinces me that Microsoft has active animus towards Jet Replication and doesn't want you to use it](http://dfenton.com/DFA/Replication/index.php?title=Things_not_to_believe_in_the_MS_documentation)'_. Anyways: [here it is](http://office.microsoft.com/en-us/access-help/CH006252684.aspx) – sehe Aug 30 '11 at 23:38

2 Answers2

1

I assume that you are talking about replicating changes in one ms-access "database" such that two instances stay in sync, As such, you'd be better off abandoning ms-access and upscaling to a single centralised database.

spender
  • 117,338
  • 33
  • 229
  • 351
1

this sounds like a bad idea all around.

The common patterns apply;

  1. use GUID id's,
  2. send offline datasets,
  3. cross fingers and look for a job that allows you to use other free tools, suited for the job http://www.microsoft.com/sqlserver/en/us/editions/express.aspx

Avoid conflict resolution (don't edit the same entities on both ends)

Edit PS. after visiting hamsaweb.net; if you need this to be web deployable on a shared host:

Community
  • 1
  • 1
sehe
  • 374,641
  • 47
  • 450
  • 633
  • Jet Replication handled all these scenarios (full merge replication) before SQL Server did, for instance. It's still a usable platform, though not without its pitfalls. – David-W-Fenton Aug 30 '11 at 21:50