| Author |
Can't RDA push one table
|
|
|
| I have one table that I can't push to the central database with SQL-CE. I
get an error message saying the table does not exist even though I can look
at it with the query analyzer, so clearly it does. Every other table pushes
correctly using the same push routine. I'm trying to get my new data
pushed back to the central database and this key table won't transfer.
This table pushes correctly on another handheld agaist a test database.
Any suggestions on what may be causing this behavior.
--
Thanks
RonF
| |
|
| Hi RonF.
Make sure that the record is compatible with the associated columns of
remote SQL Server table you pulled. Try to insert the same record directly
from SQL Query Analyzer to the table you pulled from to debug.
I got the same error and found that I was inserting a null value in a column
of the table i pulled. But that column was a part of composite key on remote
table i pulled from. So pushing back was causing a Constraint Violation and
giving the same error.
"RonF" wrote:
> I have one table that I can't push to the central database with SQL-CE. I
> get an error message saying the table does not exist even though I can look
> at it with the query analyzer, so clearly it does. Every other table pushes
> correctly using the same push routine. I'm trying to get my new data
> pushed back to the central database and this key table won't transfer.
>
> This table pushes correctly on another handheld agaist a test database.
> Any suggestions on what may be causing this behavior.
>
>
>
> --
> Thanks
> RonF
| |
|
| I've found that this table now won't push on any of my handhelds so it is not
specific to one handheld. The only thing I find unique about this table is
that it uses two columns for the primary key. I need to do this to make sure
everything is unique. Is this OK to do with RDA? I haven't found anything
in the documentation on this.
--
Thanks
RonF
"Arif" wrote:
[color=darkred]
> Hi RonF.
>
> Make sure that the record is compatible with the associated columns of
> remote SQL Server table you pulled. Try to insert the same record directly
> from SQL Query Analyzer to the table you pulled from to debug.
>
> I got the same error and found that I was inserting a null value in a column
> of the table i pulled. But that column was a part of composite key on remote
> table i pulled from. So pushing back was causing a Constraint Violation and
> giving the same error.
>
> "RonF" wrote:
>
| |
|
| Hi RonF,
1- check that you have pulled the table with option
"RdaTrackOption. TrackingOnWithIndexe
s".
2- use ip address of remote PC instead of name.
3- make sure that remote table must have at least one primary column.
if all the above things are ok and still you face problem then try with the
following:
1- in remote table put only one record and pull the table with above configs.
2- now modify any one of the columns value(but take care don't enter
incompatible type values)
3- now push back the table with option "RdaBatchOption.BatchingOn".
Now it must push the table succuessfully.
Please try and inform me.
Arif.
"RonF" wrote:
[color=darkred]
> I've found that this table now won't push on any of my handhelds so it is not
> specific to one handheld. The only thing I find unique about this table is
> that it uses two columns for the primary key. I need to do this to make sure
> everything is unique. Is this OK to do with RDA? I haven't found anything
> in the documentation on this.
> --
> Thanks
> RonF
>
>
> "Arif" wrote:
>
|
|
|
|