Re: crak for activesync 4 to allow desktoptodevice and devicetodes

RE: >> It's always the same with MS, we developers must change ....

CORRECT. And if you didn't change you would be still writing on COBOL coding
sheets . . .


"MarceloB." <MarceloB.@xxxxxxxxxxxxxxxxxxxxxxxxx> wrote in message
news:0B6B2EF0-574A-405A-865C-69A991BF82FB@xxxxxxxxxxxxxxxx
Hi everyone!

It's always the same with MS, we developers must change ....

Anyway, did you know where i can download the "ADOCE DLLs to a WM5
device"?

Has someone try "primeworks data port component"? Has someone found
something to so access-sqlce convertion?

Thanks in advance!.

MarceloB.

"MikeB" wrote:

Hi Sami,

Hang in there, although I would like to see the Microsoft Mobile devices
team be much, much more hesitant to make changes that break existing
code, I
do believe there are people there who care about the platform and listen
to
the developers. I believe we will see this issue eventually resolved for
Windows Mobile 5 and ActiveSync 4.

Mike B.

"Sami Benelhadj" <SamiBenelhadj@xxxxxxxxxxxxxxxxxxxxxxxxx> wrote in
message
news:E7B2EC97-6F14-46F2-A921-A4D423905241@xxxxxxxxxxxxxxxx

Mike,

Thanks for your answer and we accord in the fact that there is actually
a
loss in MS Access and WM5 interoperability. Anyway I think that recover
asap
basic functionalities to allow our apps run correctly on WM5 is more
urgent
than ask Microsoft for new bridges between MS Access & SQL Mobile.

Today, accept that Microsoft kill previous CE architectures
deliberately
without ascending compatibility is unbelievable and unacceptable for
developpers. We can't afford Windows Mobile earthquakes every 3 years
!!!
It's less than required time to implement and deploy reliable
applications
!!! In windows, it's more rational : let's take the example of DAO in
MS
Acces. It is known that it's obsolete but until Access 2003 it runs and
I
hope it will for a long time.

Finally, about RAPI, Microsoft considers that it "[...] provides a
convenient way to access device resources from a desktop computer
[...]".
You
can read this at this link (oct 2005) :

http://msdn.microsoft.com/library/en-us/dnppcgen/html/migration_developers_faq.asp?frame=true#migration_developers_faq_topic32

It can be considered as a proof of durability, but can we thrust them
after
al WM disillusions ?...



"MikeB" wrote:

Hi Sami,

I can't answer all of your questions but I can comment on ADOCE. If
possible I would get away from ADOCE; it is likely that it will be
broken
in whatever comes after WM5. If I recall correctly ADOCE is built on
CEDB
which I hear will also be broken in the next release. It would be
great
if
we could get new stuff like SQL Mobile without breaking our existing
code
and making developers rewrite all of their apps, but that is another
thread
altogether. I hope that someday soon we see Microsoft release a sync
provider that syncs an Access database to SQL Mobile, to replace the
functionality lost with "Pocket Access" sync.

As far as RAPI, I have questions about that too. I've asked several
times
and can't seem to get an answer as to what the future holds for RAPI.
I
use
RAPI to manipulate a CEDB database in one of my apps and I'd love to
know
what's going to happen with this. From what I understand there is no
EDB
version of RAPI but as yet I can't get confirmation on this. Anyone?

Mike B.



Bye
MikeB <web@xxxxxxxxxxxxxxx> Wed, 18 Jan 2006 16:23:55 -0500

=== Posted with Qusnetsoft NewsReader 3.3

----- Original Message -----
From: "Sami Benelhadj" <SamiBenelhadj@xxxxxxxxxxxxxxxxxxxxxxxxx> Sent:
Wed,
18 Jan 2006 14:14:46 Subject: Re: crak for activesync 4 to allow
desktoptodevice and devicetodes

Thanks Gil, Devin, etc.

Thanks to everybody for making this thread interesting : it's very
heartening to see that we are not alone and other developpers
encounter
same difficulties with Microsoft systems updates !!!

The only work around I have found if Microsoft doesn't implement an
available WM5 sync function is to reproduce programmatically
synchronization. It's not so difficult. In my case I only use
DESKTOPTODEVICE and DEVICETODESKTOP to convert mdb to cdb. Afterwards,
my
software makes the data synchronization with the server database. It's
very
easy to make this operation successefully with adding a date field to
tables. You just have to check 3 states for each records updates : new
record, modification and deletion. Finally it offers more flexibility
:
you
can manipulate indexes of server database with more control, data
transfer
from device to desktop concerns only modifications (faster than send
complete device cdb database to desktop), etc.

So the only probem that persist is mdb<>cdb conversion. The work
around
is
to make programmatically those operations (= DESKTOPTODEVICE) :
- export mdb to text files (1 by table for example),
- transfer text files to device with RAPI,
- then insert them with ADOCE in a blank cdb database on user device
software open.

DEVICETODESKTOP can be exactly the opposite.

What do you think about that ? My fears are :
- new implementation = new bugs and so new problems with cost losses
(customers are patients but we don't have to go beyond the limits !)
- ADOCE works on WM5 but seems to be obsolete (what about ADOCE and
WM6
?)
- RAPI works on WM5 but what about RAPI and WM6 ?

Please post your advices and experiences.

There is an emergency to react because our customers won't be able to
purchase Pocket PC 2003 devices in several months !

Sami (from France... that's why my english is not fluent)

"nelsonsoft@xxxxxxxxxxx" wrote:

> I am having the same problem. They have broken my program once
before
> and now again it is broken. I also use DESKTOPTODEVICE and
> DEVICETODESKTOP. Has anyone found a work around?

> Thanks,

> Gil

> Sami Benelhadj wrote:
>> Hi everybody. I'm Sami from France

>> I confirm that DESKTOPTODEVICE doesn't work with WM5 and AS4 (I've
made
>> several tests, including new version 4.1.4841 of adofiltr.dll
supplied
>> with AS4).

>> It's simply unbelievable.

>> Mobile implementations on Pocket PC are just reaching an
acceptable
>> level in industrial applications. It's very hard to introduce
those
>> tehnologies in refinery and chemistry industries because
everything
>> goes very slowly. For example, Progest for Pocket PC (http://cd.
>> concept.online.fr) has been implemented there are 3 years and
begins
to
>> be efficient only today !

>> All our mobile softwares works with ADOCE and cdb/mdb databases.
>> Without DESKTOPTODEVICE and DEVICETODESKTOP, it means that all our
>> mobile sofwares and know-how can be put to trash !!!

>> Microsoft : PLEASE HELP ! Our customers are Shell, Total, BP
(British
>> Petroleum), Arco chemicals (Lyondell), Bayer, Sanofi, etc. and
they
>> won't believe that all their deployement application efforts are
>> reduced to zero. Microsoft is a serious compagny and like other
>> industries must keep their end customers satisfied.

>> "Devin Matthews" wrote:

>>> We are having this same problem when trying to send/convert our
mdb
to
>>> a Windows Mobile 5.0 device. This is effecting our product
negitively
>>> and causing inconvenient work arounds for our customers.

>>> Is there any advice or suggestions that can be provided as an
>>> alternative solution to DESKTOPTODEVICE or a work-around so that
>>> DESKTOPTODEVICE will work?

>>> Please assist!

>>> Thanks a lot,
>>> Devin

>>> "JeffK" wrote:

>>>> Robert,
>>>> This is absolutely imperative that a soultion for this problem
comes
>>>> out soon. Over the past 2 weeks we have had to tell many of our
>>>> clients to return their PocketPCs because they will not work
with
our
>>>> app. Microsoft is hurting themselves by not having an immediate
>>>> solution for this. I am sure their are MANY vertical market
solutions
>>>> out there that are being affected by this including your own
Money
>>>> app for the PocketPC. Id there any ETA yet ?

>>>> "ryankreu" wrote:

>>>>> Any word yet on the unsupported download that includes an ADOCE
sync
>>>>> provider for AS4 and a patched set of ADOCE runtimes?

>>>>> Thanks,
>>>>> Ryan

>>>>> "Robert Levy [MS]" wrote:

>>>>>> I don't know if "a$$hattery" is how I'd describe it but you
are
>>>>>> right to point out that this is not an AS4-related issue :)

>>>>>> The ADOCE runtimes were removed from ROM on Windows Mobile 5.0
>>>>>> since that set of APIs was documented as deprecated back when
>>>>>> Pocket PC 2003 was released. You could manually add the ADOCE
DLLs
>>>>>> to a WM5 device and things will be fine - until you try to
sync
>>>>>> that database with a desktop. While syncing, there's a good
chance
>>>>>> that random bad things will happen due to a memory management
issue
>>>>>> in our code that didn't surface previous to WM5. We're working
on
>>>>>> making a unsupported download available on MSDN that includes
an
>>>>>> ADOCE sync provider for AS4 and a patched set of ADOCE
runtimes
for
>>>>>> WM5. Unfortunately, I don't have an ETA for that right now but
we
>>>>>> definitely feel your pain and are working on a solution.

>>>>>> --
>>>>>> -Robert Levy Program Manager, Windows Mobile Developer
Experience
>>>>>> http://blogs.msdn.com/windowsmobile

>>>>>> "khorad" <khor@xxxxx> wrote in message news:%23wq26d00FHA.
>>>>>> 664@xxxxxxxxxxxxxxxxxxxxxxx
>>>>>>> Yes we get the message that this is no longer supported and
we
are
>>>>>>> moving to
>>>>>>> .netcf, but we need a more immediate solution that works with
WM5
>>>>>>> devices

>>>>>>> I know the support is in there because desktoptodevice works
with
>>>>>>> ActiveSync
>>>>>>> 4 and a PPC2003 device and I know the object store still
works
on
>>>>>>> WM5

>>>>>>> Thus the only reason desktoptodevice doesn't work with
ActiveSync
>>>>>>> 4 and WM5
>>>>>>> is simple a$$hattery

>>>>>>> Thanks






.