ملف dll لتبادل البيانات مع البوكت

hi

am working in company about the same sield

so whats tour oponuon to share our exprince

لا يوجد مشكلة

و اظن ان تبادل الخبرات امر مفيد

بريدي هو

tammam84@yahoo.com

hi

and thats my email

qalaloh@yahoo.com

lets first descuse the update or replication the data from sql server in pc and Sql server ce in GPRS

حسنا و إليك مقال يبين طرق الاتصال و تبادل البيانات مع القاعدة

بالنسبة إلي فأنا سأستخدم RDA

في مشروعي من خلال وب سيرفس

Replication

For non-data-speaking folk, replication topics can be daunting because replication has its own jargon and word usage. Replication uses a publishing metaphor to refer to the individual parts and roles. It consists of publications and each publication consists of one or more articles. Servers can be set up to be both a publisher of data and a subscriber of other publications.

Each publication is made up of one or more articles and there are two kinds of articles:

Download-only articles (tables)

Partitioned (filtered) articles

On servers acting as publishers, a distribution database has to be set up. The database keeps track of all the moving parts - publications, article definitions, and all subscribers. What is kept in the metabase depends on the publishing model. Replicating to small databases and devices isn't the same as their larger cousins. Because performance and storage are issues, Microsoft revamped some of the internals around the metabase activity: If you had 500 Pocket PC devices in an office building and each subscribed to a publication, you could find yourself doing a lot of setup work under the older model. Each one would have entries that keep track of exactly where that subscriber's data is. Using the Pull model in RDA eliminates a lot of the record keeping because there's no need to keep up with the details - simply retrieve the current definition and go.

Folks who have pushed SQL replication around pretty hard over the years won't find the Transactional or Snapshot types that are available in the Enterprise product. Given the nature of what's being built I suppose that's okay. Snapshots would only be useful to populate lookup tables while Transactional would give us near real-time results,but at a near real-time price. You get something similar with RDA that works better on the small platform. If you come from a big SQL background, just think Merge Replication scenarios that can handle just about anything.

Merge Replication

You won't want for data, but you might beg for performance. We're in the major leagues of true replication here. Bidirectional (changes from either the server or client are posted on the other) means everyone with a subscription gets pretty much the same data barring the normal delays of replication. But is bidirectional required or desirable? Maybe. There's a performance hit at both ends. So? If you have the horsepower, it makes sense not to do the low-level plumbing code you need with RDA. With hardware so cheap these days it's pretty hard to make a big deal out of the slight difference.

The heart of your design decision rests with the kind of application you're building. If you want a tightly coupled application where data is updated from both the PDA and the server, Merge Replication is your friend. I think of it as a "duplicate data everywhere" strategy. It would make sense to say, add new customers to a CRM application . But even that scenario has flaws starting with the obvious: would you really add a new customer in a form on your PDA? If you did, you'd probably need a BlueTooth keyboard.

I think Web Services is the way to go when possible and might be your best answer. Using Web Services over Merge Replication will work unless there's a compelling reason to use Merge Replication.-There's less to keep up with, it's easier to implement, and there's no mess to clean up if the publication stops working.

The main class in coding for Merge Replication is System.Data.SqlServerCe.SqlCeReplication.

RDA

Remote Data Access (RDA) is great for the semi-disconnected state because the model calls for downloading static data and only uploading the changes. This is great if a SmartPhone won't have access to the network for a while. You'll need to do some kind of lookup (such as inventory) and record data in tables on the device. Once connected, pass that information back to the server.

The main class in coding for RDA replication is System.Data.SqlServerCe.SqlCeRemoteDataAccess.

hi

am know thats and am work with all thats Way

about ur project what u can do when the connection failed

out of rang

اذا اردنا ان نكمل في هذا الموضوع

اتمنى ان نيدأه في موضوع جديد

حيث انني اقدم مقالة و انت تقدم اخرى و هكذا حتى يكتمل المشروع

لذا سأطرح مشاركة بعنوان "مشروع قواعد بيانات من الالف إلى الياء"

و ضمن هذه المشاركة نتبادل و من يحب ان يقدم مشاركاته ايضا