Synchronizing tables

[Veggis]

Hi

We have this access application - which we use to register stuff into.
Most of the time we're online, and that's all right, but now we need
be able to register stuff offline, and then it would be nice if we
could copy the registered stuff into the main database when we get
online.

So basically I want to copy data from one mdb-file to another - and
these two mdb's look the same in design, but have different data. I
figured I could just copy stuff from the offline into the online and
delete everything from the offline afterwards. So I guess what I'm
looking for is some kind of synchronizing tool. I guess that's a long
shot, if you don't know that - do you know how I could connect to the
other db and through code copy everything from the offline db over
into the main database? If there are some neat sql sentences for that
I'd appreciate if you told me about them.

regards

Vegard

[David W. Fenton]

"Veggis" <ve******@gmail.comwrote in
news:11**********************@k78g2000cwa.googlegr oups.com:

We have this access application - which we use to register stuff
into. Most of the time we're online, and that's all right, but now
we need be able to register stuff offline, and then it would be
nice if we could copy the registered stuff into the main database
when we get online.

There are two ways to accomplish this:

1. have special "provisional" data entry mode for offline entry that
has to be connected to the real data, and synchronized in code, and
assigned non-provisional PKs and so forth, OR

2. use Jet Replication.

If the disconnected users can connect to the "mother ship" via LAN,
it's very easy to just use direct replication. If they can never
connect via LAN (only WAN or Internet or wireless LAN), then
indirect replication is needed. That's substantially more complex.

If I had a client present me the situation you describe, I'd go with
Jet Replication. But then, I've been doing that since 1998.

The simple scenario with laptops that are in the field and then come
back into the office is pretty easy to implement, though.

--
David W. Fenton http://www.dfenton.com/
usenet at dfenton dot com http://www.dfenton.com/DFA/

[Veggis]

Thanks a lot!
On 3 Feb, 18:26, "David W. Fenton" <[e-mail]>
wrote:

"Veggis" <[e-mail] innews:11**********************@k78g2000cwa.google groups.com:

We have this access application - which we use to register stuff
into. Most of the time we're online, and that's all right, but now
we need be able to register stuff offline, and then it would be
nice if we could copy the registered stuff into the main database
when we get online.

There are two ways to accomplish this:

1. have special "provisional" data entry mode for offline entry that
has to be connected to the real data, and synchronized in code, and
assigned non-provisional PKs and so forth, OR

2. use Jet Replication.

If the disconnected users can connect to the "mother ship" via LAN,
it's very easy to just use direct replication. If they can never
connect via LAN (only WAN or Internet or wireless LAN), then
indirect replication is needed. That's substantially more complex.

If I had a client present me the situation you describe, I'd go with
Jet Replication. But then, I've been doing that since 1998.

The simple scenario with laptops that are in the field and then come
back into the office is pretty easy to implement, though.

--
David W. Fenton http://www.dfenton.com/
usenet at dfenton dot com http://www.dfenton.com/DFA/

[Veggis]

On 3 Feb, 18:26, "David W. Fenton" <[e-mail]>

wrote:

"Veggis" <[e-mail] innews:11**********************@k78g2000cwa.google groups.com:

We have this access application - which we use to register stuff
into. Most of the time we're online, and that's all right, but now
we need be able to register stuff offline, and then it would be
nice if we could copy the registered stuff into the main database
when we get online.

There are two ways to accomplish this:

1. have special "provisional" data entry mode for offline entry that
has to be connected to the real data, and synchronized in code, and
assigned non-provisional PKs and so forth, OR

2. use Jet Replication.

If the disconnected users can connect to the "mother ship" via LAN,
it's very easy to just use direct replication. If they can never
connect via LAN (only WAN or Internet or wireless LAN), then
indirect replication is needed. That's substantially more complex.

If I had a client present me the situation you describe, I'd go with
Jet Replication. But then, I've been doing that since 1998.

The simple scenario with laptops that are in the field and then come
back into the office is pretty easy to implement, though.

--
David W. Fenton http://www.dfenton.com/
usenet at dfenton dot com http://www.dfenton.com/DFA/

Now I will try to quote correctly. I was wondering, I'm using access -
and I tried making a replica of the "main" database, now I have two
databases excactly same data - one called funtab.mdb and one called
funtab_travel.mdb. Basically my employees travel around the area going
offline, entering new assignments when offline (they sit down with a
customer and enters data), meaning each assignment gets a unique id -
getMaxID + 1 - _meanwhile_ _I_ make a new assignment at the main
database here at the office that gets the same id who was offered to
the employee who was offline.

Does jet replication solve this? I've tried this a little, and didn't
make it work so far.

I assume by jet replication you're refering to the built-in tools of
access? Or am I completely lost here?

regards

Vegard

[David W. Fenton]

"Veggis" <ve******@gmail.comwrote in
news:11**********************@n33g2000cwc.googlegr oups.com:

Now I will try to quote correctly. I was wondering, I'm using
access - and I tried making a replica of the "main" database, now
I have two databases excactly same data - one called funtab.mdb
and one called funtab_travel.mdb. Basically my employees travel
around the area going offline, entering new assignments when
offline (they sit down with a customer and enters data), meaning
each assignment gets a unique id - getMaxID + 1 - _meanwhile_ _I_
make a new assignment at the main database here at the office that
gets the same id who was offered to the employee who was offline.

Does jet replication solve this? I've tried this a little, and
didn't make it work so far.

Replication cannot solve this. You'll have to do something else to
insure the sequence is unique. There are three main options:

1. reserve blocks of numbers for each replica.

2. track the source replica as part of the unique identifier.

3. assign temporary numbers in replicas and convert them to the
final sequence in one central replica.

Which of these is the most appropriate for your app is up to you to
determine.

I assume by jet replication you're refering to the built-in tools
of access? Or am I completely lost here?

Well, Access has a simple UI for using the functionality of Jet
Replication, yes.

--
David W. Fenton http://www.dfenton.com/
usenet at dfenton dot com http://www.dfenton.com/DFA/