Wondered if anyone can help

I need to sync a access 2003 database to pocket pc - I've got activesync
3.8, primary key is setup on first column.

The import conversion setup seems to convert the data from the mdb format to
the cdb format ok but I seem to have problems using the data on the pocket pc.

If I subsequently use the explore option on activesync and copy/paste the
file from the pocket pc to say the desktop I receive data conversion errors.

If anyone can shed any light on what I'm doing wrong I'd appreciate it as
this is driving me mad.

Regards


Adam Wright

What are you using to view/manipulate the .cdb on the PPC? There isn't a
native app that does that. There are numerous third party applications
though. My favorites being DataOnTheRun, if you want basic DB functionality,
and SprintDB if you want more full-blown DB features.

Are you trying to convert the DB to the PPC format, and then convert the
PPC.cdb back to a .mdb by dragging in to and out of Mobile Explorer? Or are
you dragging the .mdb into the Mobile Explorer and following the setup steps
to establish synchronization?

"A.Wright" <AWright@discussions.microsoft.com> wrote in message
news:45EB887D-E3C8-4205-9904-06EB92D3DE77@microsoft.com...

Hi Sven

I've written a program that uses ADOCE v3.0 to read the data.

I've tried highlighting the file in pocket explorer then pasting it the pc
desktop - the active sync conversion comes up as normal but conversion errors
appear in the process.

Is it maybe that that pc database is access 2003 and I'm using adoce v3.0 to
read the data. I did find a registry setting on the pocket pc that set active
sync to set the jet version either 3.5 or 4

Regards


Adam Wright

"Sven" wrote:

I think you may be deeper into this than I have experience with. I have
noticed that when errors occur, there is a listing of what those errors
were. Did you see that and did they help any in determining the possible
source. Sometimes it's a matter of a field definition not being entirely
supported in the .cdb and thereby making the data transferred invalid.

If you are developing your own app, it may be worthwhile to check the
expertise in microsoft.public.pocketpc.developer. They may have the
Access/ADOCE/Activesync/.cdb issues more at hand. I got a little confused as
to whether the errors were happening when you dragged the .mdb to the PPC or
when you dragged the .cdb back to the desktop (assuming you aren't setting
this up to sync). Maybe clarify that a bit if you ask the developers. From
my view, if it is from PC to PPC, it may have something to do with the
Access 2003 interaction with the ActiveSync conversion filter. Are you using
AS 3.8?

"A.Wright" <AWright@discussions.microsoft.com> wrote in message
news:49000F69-BB11-4DB3-93EF-3DC61CA75808@microsoft.com...

Hi

I am using activesync 3.8, I'm thinking of trying access 2000 or earlier to
see if it's a 2003 > pocket accesss problem. It does seem to convert ok the
one way from PC to pocket pc ok with no errors.

Regards




"Sven" wrote: