Re: crak for activesync 4 to allow desktoptodevice and devicetodes

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


Sure, but, it does get old re-coding all of your apps. Considering
that the pace of change in the Pocket PC operating systems has been
much more rapid vs. the desktop OS, and that most Pocket PC developers
are individuals or small companies, I'd like to see more reluctance to
break existing apps. Many apps had to be redesigned to work with
Windows Mobile 5. The CEDB database structure changed from Pocket PC
2002 to 2003. Now we are going to break CEDB apps altogether in the
next release after Windows Mobile 5. Existing RAPI apps certainly have
difficulties with Windows Mobile 5, and that's not even considering
there isn't a RAPI way to access the EDB databases. MFC code that
works fine on even Windows Mobile 5 devices won't compile in VS 2005
since things like CCeDBDatabase and CBitmapButton are not included.
Anyone have a project from eVC++ that imported without errors into
Visual Studio 2005??? Also, in the case of the Pocket Access
snchronization, it really has not been replaced by anything. On the
desktop you can dig up old software that you used many years ago and in
most cases you can still run it on modern computers. I'd like to see
the same kind of compatibility in the mobile world.

Sorry, just had to vent there.... :-)

Mike B.

.