sqlce versions, compatibility

[dev100]

Hi, we are currently targeting sql ce 3.1 with cf 2.0 app as it is in the
rom of devices and our customerwants us not to deploy 3.5. However if the
next version of WM devices has sql ce 3.5 in rom as opposed to sql ce 3.1,
does this mean we now need to deploy sql ce 3.1 binaries ie there is no
backwards compatibilty?



__________ Information from ESET Smart Security, version of virus signature database 4108 (20090527) __________

The message was checked by ESET Smart Security.

http://www.eset.com

 

[Ginny Caughey MVP]

With SqlCe there is generally no backwards compatibility for databases built
with prior versions. For that reason what I do, and what I recommend you
suggest to your customer, is that it is safest to always go with the newest
version of SqlCe and include the 1 - 1.5 Mb dlls it requires along with your
app. Whatever the next version of WM includes in ROM for SqlCe, there will
always be a next one after that which could be different. This approach also
gives you the advantage of the latest bug fixes in SqlCe.

 

[Ginny Caughey MVP]

With SqlCe there is generally no backwards compatibility for databases built
with prior versions. For that reason what I do, and what I recommend you
suggest to your customer, is that it is safest to always go with the newest
version of SqlCe and include the 1 - 1.5 Mb dlls it requires along with your
app. Whatever the next version of WM includes in ROM for SqlCe, there will
always be a next one after that which could be different. This approach also
gives you the advantage of the latest bug fixes in SqlCe.

 

[dev100]

many thanks

With SqlCe there is generally no backwards compatibility for databases
built with prior versions. For that reason what I do, and what I recommend
you suggest to your customer, is that it is safest to always go with the
newest version of SqlCe and include the 1 - 1.5 Mb dlls it requires along
with your app. Whatever the next version of WM includes in ROM for SqlCe,
there will always be a next one after that which could be different. This
approach also gives you the advantage of the latest bug fixes in SqlCe.

--

Ginny Caughey
Device Application Development MVP





__________ Information from ESET Smart Security, version of virus
signature database 4108 (20090527) __________

The message was checked by ESET Smart Security.

http://www.eset.com

__________ Information from ESET Smart Security, version of virus signature database 4108 (20090527) __________

The message was checked by ESET Smart Security.

http://www.eset.com

 

[dev100]

many thanks

With SqlCe there is generally no backwards compatibility for databases
built with prior versions. For that reason what I do, and what I recommend
you suggest to your customer, is that it is safest to always go with the
newest version of SqlCe and include the 1 - 1.5 Mb dlls it requires along
with your app. Whatever the next version of WM includes in ROM for SqlCe,
there will always be a next one after that which could be different. This
approach also gives you the advantage of the latest bug fixes in SqlCe.

--

Ginny Caughey
Device Application Development MVP





__________ Information from ESET Smart Security, version of virus
signature database 4108 (20090527) __________

The message was checked by ESET Smart Security.

http://www.eset.com

__________ Information from ESET Smart Security, version of virus signature database 4108 (20090527) __________

The message was checked by ESET Smart Security.

http://www.eset.com