G
Guest
I am working on a mobile application using SQL Mobile 2005 and merge
replication to SQL 2000 SP4 under VS 2005 Beta 1 (will shortly be moving over
to Beta 2).
I was very excited to use SQL Mobile since it allows for multi-user stuff
instead of single connections like SQL CE 2.0. I am running into an
interesting problem though using ResultSets.
Upon launching the application, if the sychronization process is run before
any DB ResultSet calls it can apparently sync. If any ResultSets are called
before sychronization SQL Mobile acts like the DB is unavailable when the
sync is called.
To prove the concepts of mobile DB to the execs I have reverted to DataSets
and opening/closing SQLCeConnection objects to the DB, but the speed of the
ResultSets and the mluti-user features would be nice to use.
Ideally, I would like to be able to call the sync process and have that run
in the background on the device while allowing the user to continue to move
forward with processing data. Does the merge replication sync process lock
the DB in anyway under SQL Mobile that would prevent me from being able to
accomplish this, particularly while using ResultsSets?
I am not sure if the issues I have experienced are the result of Beta 1, or
if I have done something wrong. The difference between Beta 1 and Beta 2 are
not insignificant in the things I have seen so far (no RichInk type for
starters) and moving code into Beta 2 is not entirely straightforward, so I
am still working on being able to test ResultSets again, but if anyone has
experience with this and can give me some pointers I would appreciate it!
Thanks!
replication to SQL 2000 SP4 under VS 2005 Beta 1 (will shortly be moving over
to Beta 2).
I was very excited to use SQL Mobile since it allows for multi-user stuff
instead of single connections like SQL CE 2.0. I am running into an
interesting problem though using ResultSets.
Upon launching the application, if the sychronization process is run before
any DB ResultSet calls it can apparently sync. If any ResultSets are called
before sychronization SQL Mobile acts like the DB is unavailable when the
sync is called.
To prove the concepts of mobile DB to the execs I have reverted to DataSets
and opening/closing SQLCeConnection objects to the DB, but the speed of the
ResultSets and the mluti-user features would be nice to use.
Ideally, I would like to be able to call the sync process and have that run
in the background on the device while allowing the user to continue to move
forward with processing data. Does the merge replication sync process lock
the DB in anyway under SQL Mobile that would prevent me from being able to
accomplish this, particularly while using ResultsSets?
I am not sure if the issues I have experienced are the result of Beta 1, or
if I have done something wrong. The difference between Beta 1 and Beta 2 are
not insignificant in the things I have seen so far (no RichInk type for
starters) and moving code into Beta 2 is not entirely straightforward, so I
am still working on being able to test ResultSets again, but if anyone has
experience with this and can give me some pointers I would appreciate it!
Thanks!