Access Database transactional replicated into SQL Server 2000

I have an access database that I want to transactionally replicate
into SQL Server 2000. Can someone point me in the right direction for
getting the source connection in enterprise manager? Or a brief
example o how to start this? Have looked at SQL to SQL, but not Access
to SQL.
Thanks John
This can't be done easily. You can replicate from SQL Server 2000 to an
Access database if you create an odbc datasource subscriber. Have a look at
this to get an idea of how it is done.
http://www.nwsu.com/lowres_replication_ch02.pdf
You could create a merge publication on your SQL Server and create the
Access database as a subscriber. This will replicate the changes in the
access database back to SQL Server.
<freeman642@.gmail.com> wrote in message
news:1180004621.496305.101600@.p47g2000hsd.googlegr oups.com...
>I have an access database that I want to transactionally replicate
> into SQL Server 2000. Can someone point me in the right direction for
> getting the source connection in enterprise manager? Or a brief
> example o how to start this? Have looked at SQL to SQL, but not Access
> to SQL.
> Thanks John
>
|||thanks Hilary thats a great idea. Never thought of that. thanks John
On 24 May, 13:16, "Hilary Cotter" <hilary.cot...@.gmail.com> wrote:
> This can't be done easily. You can replicate from SQL Server 2000 to an
> Access database if you create an odbc datasource subscriber. Have a look at
> this to get an idea of how it is done.http://www.nwsu.com/lowres_replication_ch02.pdf
> You could create a merge publication on your SQL Server and create the
> Access database as a subscriber. This will replicate the changes in the
> access database back to SQL Server.
> <freeman...@.gmail.com> wrote in message
> news:1180004621.496305.101600@.p47g2000hsd.googlegr oups.com...
>
>
> - Show quoted text -
sql

Access 2000 merge repl problems

Hello,,
for three days i am trying to figure out howto get replication with merge
between sql server en access2K.
Transactional replication is working, but I need a configuration which is
independant of the network, so I need the Merge.
I find all kind of descriptions on the net, but none of them are a
straight-forward solution for the Merge.
Sometimes i get problems with authorization, other times the original MDB
is renamed to <original>_old.mdb or the column names cannot be found (?
)
Please help , i am getting desparate of this.
Any help : very welcome
thanks,
roel
I believe when you are replicating to an access database over the network
you get the renaming phenomena you have experieinced.
Can you also check out this kb article to see if it explains your problem
with missing column names?
http://support.microsoft.com/default...b;en-us;299314
Hilary Cotter
Looking for a SQL Server replication book?
http://www.nwsu.com/0974973602.html
"roel otten" <roelo@.xs4all.nl> wrote in message
news:41d02b36$0$1580$e4fe514c@.dreader19.news.xs4al l.nl...
> Hello,,
> for three days i am trying to figure out howto get replication with merge
> between sql server en access2K.
> Transactional replication is working, but I need a configuration which is
> independant of the network, so I need the Merge.
> I find all kind of descriptions on the net, but none of them are a
> straight-forward solution for the Merge.
> Sometimes i get problems with authorization, other times the original MDB
> is renamed to <original>_old.mdb or the column names cannot be found (?
> )
> Please help , i am getting desparate of this.
> Any help : very welcome
> thanks,
> roel
>
|||Hello Hillary
thanks for your reaction
problems stay the same :
i have sql server 2k sp3
simple table1 : myid = unique identifier
text = text
i have empty c:\rep.mdb
- i make mydb as oledb / jet4.0 linked served
- i make push subscription
- snapshot starts working, is fine
- merge agent starts:
rep.mdb -> rep_old.mdb
table1 is added
error messages : could not find column MYID
In rep.mdb is table1 with MYID column, text and three added columns for
replication
also some extra tables for replicatin
al these replication items stay empty
after some time (?) the rep_old.mdb is gone and a rep.mdb is created with the
table1 snapshot.
Only changes made in Sql Server survive.
I also checked the microsft solution to change the msrpjt40.dll to the
version they say , but is is older than
the one i have ( i have version 4.10.6912.0 and they recommend 4.10.4320.0 )
any clue ?
everything is welcome
roel otten
In article <O41GyRD7EHA.2592@.TK2MSFTNGP09.phx.gbl>, hilary.cotter@.gmail.com
says...
>
>I believe when you are replicating to an access database over the network
>you get the renaming phenomena you have experieinced.
>Can you also check out this kb article to see if it explains your problem
>with missing column names?
>http://support.microsoft.com/default...b;en-us;299314
>--
>Hilary Cotter
>Looking for a SQL Server replication book?
>http://www.nwsu.com/0974973602.html
>"roel otten" <roelo@.xs4all.nl> wrote in message
>news:41d02b36$0$1580$e4fe514c@.dreader19.news.xs4a ll.nl...
>
|||any way you could post the schema for the tables you are replicating here?
Hilary Cotter
Looking for a SQL Server replication book?
http://www.nwsu.com/0974973602.html
"roel otten" <roelo@.xs4all.nl> wrote in message
news:41d14264$0$8497$e4fe514c@.dreader16.news.xs4al l.nl...
> Hello Hillary
> thanks for your reaction
> problems stay the same :
> i have sql server 2k sp3
> simple table1 : myid = unique identifier
> text = text
> i have empty c:\rep.mdb
>
> - i make mydb as oledb / jet4.0 linked served
> - i make push subscription
> - snapshot starts working, is fine
> - merge agent starts:
> rep.mdb -> rep_old.mdb
> table1 is added
> error messages : could not find column MYID
> In rep.mdb is table1 with MYID column, text and three added columns for
> replication
> also some extra tables for replicatin
> al these replication items stay empty
> after some time (?) the rep_old.mdb is gone and a rep.mdb is created with
the
> table1 snapshot.
> Only changes made in Sql Server survive.
>
> I also checked the microsft solution to change the msrpjt40.dll to the
> version they say , but is is older than
> the one i have ( i have version 4.10.6912.0 and they recommend
4.10.4320.0 )
>
> any clue ?
> everything is welcome
> roel otten
>
> In article <O41GyRD7EHA.2592@.TK2MSFTNGP09.phx.gbl>,
hilary.cotter@.gmail.com[vbcol=seagreen]
> says...
merge[vbcol=seagreen]
is[vbcol=seagreen]
MDB[vbcol=seagreen]
(?
>
|||Hi Hilary
Here is the scripting of the table i want to merge to Access :
CREATE TABLE [dbo].[Table1] (
[MyId] uniqueidentifier ROWGUIDCOL NOT NULL ,
[Tekst] [nvarchar] (50) COLLATE Latin1_General_CI_AS NULL
) ON [PRIMARY]
I realize thta there is no 'Not for replication' item with the
unique identifier, is it not added by the wizards ?
regards,
roel
In article <ePs1EwO7EHA.2156@.TK2MSFTNGP10.phx.gbl>, hilary.cotter@.gmail.com
says...
>
>any way you could post the schema for the tables you are replicating here?
>--
>Hilary Cotter
>Looking for a SQL Server replication book?
>http://www.nwsu.com/0974973602.html
>"roel otten" <roelo@.xs4all.nl> wrote in message
>news:41d14264$0$8497$e4fe514c@.dreader16.news.xs4a ll.nl...
>the
>4.10.4320.0 )
>hilary.cotter@.gmail.com
>merge
>is
>MDB
>(?
>
|||you will have to change table1 to look like this:
CREATE TABLE [dbo].[Table1] (
[MyId] [uniqueidentifier] NOT NULL ,
[Tekst] [nvarchar] (50) COLLATE Latin1_General_CI_AS NULL ,
[rowguid] uniqueidentifier ROWGUIDCOL NOT NULL
) ON [PRIMARY]
GO
Hilary Cotter
Looking for a SQL Server replication book?
http://www.nwsu.com/0974973602.html
"roel otten" <roelo@.xs4all.nl> wrote in message
news:41d17dc3$0$30525$e4fe514c@.dreader20.news.xs4a ll.nl...
> Hi Hilary
> Here is the scripting of the table i want to merge to Access :
> CREATE TABLE [dbo].[Table1] (
> [MyId] uniqueidentifier ROWGUIDCOL NOT NULL ,
> [Tekst] [nvarchar] (50) COLLATE Latin1_General_CI_AS NULL
> ) ON [PRIMARY]
>
> I realize thta there is no 'Not for replication' item with the
> unique identifier, is it not added by the wizards ?
> regards,
> roel
>
>
> In article <ePs1EwO7EHA.2156@.TK2MSFTNGP10.phx.gbl>,
hilary.cotter@.gmail.com[vbcol=seagreen]
> says...
here?[vbcol=seagreen]
with[vbcol=seagreen]
network[vbcol=seagreen]
problem[vbcol=seagreen]
which[vbcol=seagreen]
original
>

about transactional replication

Hi,
I have created a transactional replication on SQL Server 2000 with SP3. Only
one database is being published with 70 tables.
But when it begins to replicate data the following errors occured
""The process could not bulk copy into table 'tablename' ""
Violation of PRIMARY KEY constraint 'tablename_PKEY'. Cannot insert
duplicate key in object 'tablename'.
This table has a PKEY and it's not identity and this table also related with
other tables
This question is asked before but i have still no idea to solve this problem
without deleting the relationships of that table.
Please tell the solution step by step,
Best regards...
its hard to say what is going on here. There are a couple of possibilities:
1) data already exists at the subscriber and you are not deleting it before
sending over a new snapshot.
2) you are replicating two or more articles to the same object on the
subscriber.
3) you are getting a different error message than the one posted.
Are you replicating the DRI of these tables, or are you replicating to a
database where the schema already exists? If so you will need to send a
pre-snapshot command which disables all DRI, and a post snapshot command
which re-enables it.
Hilary Cotter
Looking for a SQL Server replication book?
http://www.nwsu.com/0974973602.html
Looking for a FAQ on Indexing Services/SQL FTS
http://www.indexserverfaq.com
"Ugur Ekinci" <ugur@.argeset.com> wrote in message
news:OUdrkjtKFHA.2688@.TK2MSFTNGP15.phx.gbl...
> Hi,
> I have created a transactional replication on SQL Server 2000 with SP3.
Only
> one database is being published with 70 tables.
> But when it begins to replicate data the following errors occured
> ""The process could not bulk copy into table 'tablename' ""
> Violation of PRIMARY KEY constraint 'tablename_PKEY'. Cannot insert
> duplicate key in object 'tablename'.
> This table has a PKEY and it's not identity and this table also related
with
> other tables
> This question is asked before but i have still no idea to solve this
problem
> without deleting the relationships of that table.
> Please tell the solution step by step,
> Best regards...
>
|||Hi Mr. Hilary,
Yes data already exists at the subscriber, how can i provide to delete
record before replicate it ?
how can I disable DRI and reenable it after replicaiton finished ?
It would be great if you give an example,
Best regards...
"Hilary Cotter" <hilary.cotter@.gmail.com>, haber iletisinde unlar
yazd:ulKrEeuKFHA.3616@.TK2MSFTNGP09.phx.gbl...
> its hard to say what is going on here. There are a couple of
> possibilities:
> 1) data already exists at the subscriber and you are not deleting it
> before
> sending over a new snapshot.
> 2) you are replicating two or more articles to the same object on the
> subscriber.
> 3) you are getting a different error message than the one posted.
> Are you replicating the DRI of these tables, or are you replicating to a
> database where the schema already exists? If so you will need to send a
> pre-snapshot command which disables all DRI, and a post snapshot command
> which re-enables it.
> --
> Hilary Cotter
> Looking for a SQL Server replication book?
> http://www.nwsu.com/0974973602.html
> Looking for a FAQ on Indexing Services/SQL FTS
> http://www.indexserverfaq.com
> "Ugur Ekinci" <ugur@.argeset.com> wrote in message
> news:OUdrkjtKFHA.2688@.TK2MSFTNGP15.phx.gbl...
> Only
> with
> problem
>
|||It's ok, thanks Mr. Hilary,
Since i checked the "delete data in the existing table..." from publication
properties , that error does not occur ,
But I need to know that can we disable DRI with SP_ commands and enable it
again ?
Best regards...
"Hilary Cotter" <hilary.cotter@.gmail.com>, haber iletisinde unlar
yazd:ulKrEeuKFHA.3616@.TK2MSFTNGP09.phx.gbl...
> its hard to say what is going on here. There are a couple of
> possibilities:
> 1) data already exists at the subscriber and you are not deleting it
> before
> sending over a new snapshot.
> 2) you are replicating two or more articles to the same object on the
> subscriber.
> 3) you are getting a different error message than the one posted.
> Are you replicating the DRI of these tables, or are you replicating to a
> database where the schema already exists? If so you will need to send a
> pre-snapshot command which disables all DRI, and a post snapshot command
> which re-enables it.
> --
> Hilary Cotter
> Looking for a SQL Server replication book?
> http://www.nwsu.com/0974973602.html
> Looking for a FAQ on Indexing Services/SQL FTS
> http://www.indexserverfaq.com
> "Ugur Ekinci" <ugur@.argeset.com> wrote in message
> news:OUdrkjtKFHA.2688@.TK2MSFTNGP15.phx.gbl...
> Only
> with
> problem
>

about MSRepl_commands Table

Hi,
We're running sql2000 with transactional replication. I found that the
system table distribution.msrepl_commands has over 3 million records. So, I
execute the command "EXEC dbo.sp_MSdistribution_cleanup @.min_distretention =
0, @.max_distretention = 0" manually. As the result, the no. of records still
remain 2.5 million records. Why? I checked with distribution clean jobs was
success everytime. How can I minimize the table size?
Thx!
Ron
are you using anonymous subscriptions? If so this might explain what you are
seeing? Also are your distribution agents running frequently? Are any of
them stopped. The clean up normally happens when they run.
Hilary Cotter
Looking for a SQL Server replication book?
http://www.nwsu.com/0974973602.html
Looking for a FAQ on Indexing Services/SQL FTS
http://www.indexserverfaq.com
"555 Rider" <ronchukw@.yahoo.com> wrote in message
news:utuLdwbhFHA.1252@.TK2MSFTNGP09.phx.gbl...
> Hi,
> We're running sql2000 with transactional replication. I found that the
> system table distribution.msrepl_commands has over 3 million records. So,
> I execute the command "EXEC dbo.sp_MSdistribution_cleanup
> @.min_distretention = 0, @.max_distretention = 0" manually. As the result,
> the no. of records still remain 2.5 million records. Why? I checked with
> distribution clean jobs was success everytime. How can I minimize the
> table size?
> Thx!
> Ron
>
|||Yes! I'm using anonymous subscriptions and clean up every 3 hours. The clean
up jobs seems to work success according to the status of SQLServer Agent.
Any things I can do to minimize the size?
Ron
"Hilary Cotter" <hilary.cotter@.gmail.com> glsD:%23sBgbIchFHA.1252@.TK2MSFTNGP09.phx .gbl...
> are you using anonymous subscriptions? If so this might explain what you
> are seeing? Also are your distribution agents running frequently? Are any
> of them stopped. The clean up normally happens when they run.
> --
> Hilary Cotter
> Looking for a SQL Server replication book?
> http://www.nwsu.com/0974973602.html
> Looking for a FAQ on Indexing Services/SQL FTS
> http://www.indexserverfaq.com
> "555 Rider" <ronchukw@.yahoo.com> wrote in message
> news:utuLdwbhFHA.1252@.TK2MSFTNGP09.phx.gbl...
>
|||query distribution.dbo.MSdistribution_status
Are most the command delivered or waiting to be delivered? If they are
waiting to be delivered you should look at improving the performance of your
distribution agents, like using pull subscriptions and changing the
PollingInterval to 1,
If the commands are mostly delivered, your problem truly is with them being
cleaned up; try to have the distribution clean up agent run every 10
minutes.
Hilary Cotter
Looking for a SQL Server replication book?
http://www.nwsu.com/0974973602.html
Looking for a FAQ on Indexing Services/SQL FTS
http://www.indexserverfaq.com
"555 Rider" <ronchukw@.yahoo.com> wrote in message
news:ex7unWchFHA.1248@.TK2MSFTNGP12.phx.gbl...
> Yes! I'm using anonymous subscriptions and clean up every 3 hours. The
clean
> up jobs seems to work success according to the status of SQLServer Agent.
> Any things I can do to minimize the size?
> Ron
>
> "Hilary Cotter" <hilary.cotter@.gmail.com>
glsD:%23sBgbIchFHA.1252@.TK2MSFTNGP09.phx .gbl...[vbcol=seagreen]
any[vbcol=seagreen]
So,[vbcol=seagreen]
result,[vbcol=seagreen]
with
>

ABout identity column in replication

Hi Guys,
I read the microsoft article about how to handle the identity column in
replication. There is sentence: " If you are using transactional replication
with the immediate-updating Subscribers option, do not use the IDENTITY NOT
FOR REPLICATION design." That means I can not use the IDENTITY NOT FOR
REPLICATION option when I want to use transactional replication with the
immediate-updating Subscribers options, is that correct? That also means I
cannot created identity column in subscriber, right? If I do need to create
identity column in the subscriber, how can I work around? Thanks
This isn't correct. If you have immediate updating you don't need NFR as the
transaction is applied on the publisher before the subscriber.
You can use NFR and identity columns on the subscriber, however, but it is
not necessary.
Hilary Cotter
Looking for a SQL Server replication book?
http://www.nwsu.com/0974973602.html
Looking for a FAQ on Indexing Services/SQL FTS
http://www.indexserverfaq.com
"Iter" <Iter@.discussions.microsoft.com> wrote in message
news:43F4ECD0-EDC3-4932-AF29-C2782E66CEDD@.microsoft.com...
> Hi Guys,
> I read the microsoft article about how to handle the identity column in
> replication. There is sentence: " If you are using transactional
> replication
> with the immediate-updating Subscribers option, do not use the IDENTITY
> NOT
> FOR REPLICATION design." That means I can not use the IDENTITY NOT FOR
> REPLICATION option when I want to use transactional replication with the
> immediate-updating Subscribers options, is that correct? That also means I
> cannot created identity column in subscriber, right? If I do need to
> create
> identity column in the subscriber, how can I work around? Thanks

About Design Requirements for Replication across different DBMS's...

you can do snapshot and transactional replication to mysql through an odbc
datasource.
SQLCE only supports merge replication.
Are you trying to replicate from SQLCE to MySQL using merge? This isn't
supported by Microsoft.
Not only do you have connection problems but other problems with database
consistency. You replicate to SQLCE using an isapi extension. Your going to
have to write something in Visual C++ to connect the two database.
Addressing your sync statement.
You can use identity columns instead of GUIDs, MySQL does support identity.
There are a lot of problems with you approach. The main problem is how do
you handle conflicts? You are only replicating new records, but what about
updqated records or inserted records?
Suppose you delete a record on the CE device, then you read records on
MySQL, the deleted record is still on MySQL so its sent back to the SQL CE
device.
I think you are trying to roll your own merge replication. Good luck.
"Sky" <forums@.xact-solutions.removethis.com> wrote in message
news:ehtSzCKGEHA.2876@.TK2MSFTNGP09.phx.gbl...
> Hello:
> I've been musing about the requirements of making a CE port of an
> application I wrote so that the data (a classic tasks/project set of
tables)
> can be carried on a CE.
> My questions are... I know that CE and MSDE have a replication feature,
but
> what about replicating to other database systems (MySQL in this case).
> I've been trying to think of what needs to be modified in the schema
design
> to allow this to work correctly.
> My first obversations are that
> a) Autoincrement ID columns are probably a dead-end as they will get out
of
> sequence if they are generated on both the CE and the desktop. Therefore a
> GUID Primary Key column seems to be more in order.
> b) The tables all need some form of LastEdited datetime column
> c) I believe that in NET you can connect to two different providers and
the
> following would work (real rough proxycode -- I never can write INNER JOIN
> statements on the fly without trial and error, but here goes):
> Step 1: Get New records on Server:
> SELECT ServerConnection.MyTable.GUID
> FROM ServerConn.MyTable,
> ServerConn.MyTable.GUID
> INNER JOIN
> ON CEConn.MyTable.GUID
> WHERE CEConn.MyTable.GUID=NULL
> These we write to the CE client.
> Step 2: Reverse Step 1 to write any NEW records on CE to Server
> Step 3: Then get any records on server that were edited later than the
CE's:
> SELECT ServerConnection.MyTable.GUID
> FROM ServerConn.MyTable, CEConn.MyTable
> WHERE ServerConn.MyTable.GUID=CEConn.MyTable.GUID
> AND (ServerConn.MyTable.LastEdited > CEConn.MyTable.LastEdited)
> Step 4: Reverse the process to write any new records from the CE to the
> server.
>
> I think that about covers it...Any changes made on the CE done at a
earlier
> date than changes also done on the server are crushed by the Server who
has
> higher priority...
>
> What I would like to know is whether anybody has dealt with this kind of
> mess before and can give pointers on how to do it.
> For example -- does anybody have a fair idea of how Palm Pilot sychronizes
> their records?
> Is there an ODBC schema field that exists per row, cross-platform, that is
> the equivalent of DateLastModified so that I don't have to add it to each
> table?
> As you can see -- I'm at the preliminary stages of this, and any advice,
> tips, articles, code samples that you can point me to would be greatly
> appreciated.
> Thank you!
>
>
Thanks for the heads up about the Deleted records. Hum.
Obviously due to your statement
<<<Are you trying to replicate from SQLCE to MySQL using merge? This isn't
supported by Microsoft.>>
I am going to have to roll my own...which I agree is not going to be easy.
But must. I can't stand it anymore not being able to synch between different
DBMS's and want to find out where I can find a good article/code example as
to how someone goes about doing it.
It has been done before -- eg: Palm, Outlook CE, etc.
So it's not impossible. Just need help to get started.
For example -- once again, stabbing in the dark -- maybe a sys table
needs to be created called Deleted
GUID : TableName : ForeignGUID : DateDeleted
So that when a Delete FROM 'task' WHERE ID='...' one has to log it
in the Deleted table...
although this works only when deleting records one at a time (would get out
of whack if the statement were simply DELETE FROM task where Subject='xxx'.)
Or all delete statements in the program have to be modified to delete the
fields in three steps (get the ID of what you want to delete first, write
those to the deleted table, then delete the records...)
Not easy. At all.
;-(
"Hilary Cotter" <hilaryk@.att.net> wrote in message
news:OI%236$fLGEHA.2980@.TK2MSFTNGP09.phx.gbl...
> you can do snapshot and transactional replication to mysql through an odbc
> datasource.
> SQLCE only supports merge replication.
> Are you trying to replicate from SQLCE to MySQL using merge? This isn't
> supported by Microsoft.
> Not only do you have connection problems but other problems with database
> consistency. You replicate to SQLCE using an isapi extension. Your going
to
> have to write something in Visual C++ to connect the two database.
> Addressing your sync statement.
> You can use identity columns instead of GUIDs, MySQL does support
identity.
> There are a lot of problems with you approach. The main problem is how do
> you handle conflicts? You are only replicating new records, but what about
> updqated records or inserted records?
> Suppose you delete a record on the CE device, then you read records on
> MySQL, the deleted record is still on MySQL so its sent back to the SQL CE
> device.
> I think you are trying to roll your own merge replication. Good luck.
>
> "Sky" <forums@.xact-solutions.removethis.com> wrote in message
> news:ehtSzCKGEHA.2876@.TK2MSFTNGP09.phx.gbl...
> tables)
> but
> design
> of
a
> the
JOIN
> CE's:
> earlier
> has
sychronizes
is
each
>
|||Hi Hilary: addendum...
Just came across some info at:
http://www.xpinneret.com/cwu09-01.html
which was about the Palm pilot, but it did clear up some issues.
I still would need an identity column, a DateLastModified, but I have to add
a byte column.
The palm pilots was simply 4 bytes:
dirty (ie: modified)
secret
locked
deleted
In other words, one simply modifies the SQL statements to "SELECT * from
table where id=... AND deleted=false (I havn't yet figured out how to write
the bit checking part in cross platform sql, but you get the point).
And instead of using a traditional DELETE statement, making it an UPDATE
statement that modifies the bit. Quite easy for that step.
Then we are back to synchronization (the article didn't cover that ;-( ) but
I think I am starting to get a less hazy view of what we're talking about...
"Hilary Cotter" <hilaryk@.att.net> wrote in message
news:OI%236$fLGEHA.2980@.TK2MSFTNGP09.phx.gbl...
> you can do snapshot and transactional replication to mysql through an odbc
> datasource.
> SQLCE only supports merge replication.
> Are you trying to replicate from SQLCE to MySQL using merge? This isn't
> supported by Microsoft.
> Not only do you have connection problems but other problems with database
> consistency. You replicate to SQLCE using an isapi extension. Your going
to
> have to write something in Visual C++ to connect the two database.
> Addressing your sync statement.
> You can use identity columns instead of GUIDs, MySQL does support
identity.
> There are a lot of problems with you approach. The main problem is how do
> you handle conflicts? You are only replicating new records, but what about
> updqated records or inserted records?
> Suppose you delete a record on the CE device, then you read records on
> MySQL, the deleted record is still on MySQL so its sent back to the SQL CE
> device.
> I think you are trying to roll your own merge replication. Good luck.
>
> "Sky" <forums@.xact-solutions.removethis.com> wrote in message
> news:ehtSzCKGEHA.2876@.TK2MSFTNGP09.phx.gbl...
> tables)
> but
> design
> of
a
> the
JOIN
> CE's:
> earlier
> has
sychronizes
is
each
>