Synchronizing Databases

[puterco]

I have a situation where our "Customer" DB is on a server and everyone at the office run the DB over appletalk etc. Sometimes though we have to take our laptops, palms etc and go see a customer on the field. So we need a copy of the "customer" DB on our own HDs in order to update it on the field (TCP/IP connections only work for a handful of people) so I'm looking for a way to easily sync the database on the laptop HD and the server when one comes back to the office. The problem is that the DB on the server changes a lot and if our consultant has been on the road for a few days he can't just import his DB on the server. One problem is that each customer has a unique ID and if we have added 5 cards to the serverDB (auto enter serial) and our consultant has added one client then we have duplicate ID on the Laptop. In this case we would have to create a new record and import the information to it but is there a way to automatically change the duplicate ID to the next free one on the server DB?

Is REAL synchronizing a difficult thing to do since it's a feature we really need to implement to our solution. I checked scriptology for tips but I didn't find anything special. If anyone knows any solutions please post a reply. (I'll go check scriptology once again while hoping for someone to reply) TIA

[puterco]

Hi, I just did couple of searches and browsed through couple of other sites and what I've found is that REAL synchronizing is way too difficult for me to implement to our first solutions release (multiple DBs to synchronize with the main DB located on the server while the main DB also keeps constantly changing). I did find the info I was looking for so don't bother posting any replies unless you've found a solution which will ease the living of all FM developers...

(The search feature of this forum is great)

[LiveOak]

Just a comment for all readers. Synchronization is hyped as a feature by so many applications that one would think it is a simple proposition. The problem with REAL WORLD synchronization is that if two different changes are made in the same record/field of two remote copies AND the most senior clerical in you company can't figure out which is correct, how does software stand a chance? Kind of like herbal medications, no lack of advertised promises.

-bd

[eremaut]

Hi,

Fully agree with LiveOak. We have found our solution via a Citrix server.

It's always in sync and it's very fast (even over the internet) ...

Only drawback is the cost, but a good sync-tool (they exist) is also very costly!

Greetings from Belgium,

Erwin

[puterco]

Good point Liveoak. I though about that one myself and I also stumbled on couple of other minor problems like Unique IDs, etc. Most likely I'm going to implement some sort of manual import/export feature which allows the user to simply add new records etc to the database, I think I'll leave the rest to plain manual input at least for this first release of our solution.

As I browsed through this site I came across very good points and if anyone is interested about this topic I suggest they do a complete search of this site using words like "sync" or "synchronization". There were tons of great posts...