What's your opinion about ADODB vs SQLCE API?

  • Thread starter Thread starter Guest
  • Start date Start date
G

Guest

Hi All!!!

Assuming that:

1. ADODB (using late binding) is full supported in the Compact Framework,
2. The development platform is VB.NET 2003,
3. No fancy controls are allowed to be used but the ones included in the
VS.NET (and only some of them)...

What is your opinion about using ADODB versus the SQLCE Library?

Long story short, in order to migrate a scary-size application from VB6
& SQL 7 to .NET & Compact Framework in a scarier time frame, I had to created
an implementation/emulation of ADODB using polimorfism. The end result is
quite good and fullfills its needs. Now, I need to start a brand-new
application for WinCE & PPC, and I'm not quite sure if using the SQLCE API
directly is the best option. Here are my thoughts:

On one side, If I re-use the ADODB implementation, I will be able to
access any database type without changing any code. Also, I can migrate to
other platforms if required (e.g. migrating from VB6 to CF was possible an
not as painfull as it might be). More over, I can implement some recovery
routines (I have experimented some little sporadic issues with select
statements that can be solved by just retrying the application).

However, on the other side, I was told in an MS Chat that SQLCE is the
way to go and that the future of mobile applications is there, and that
ADODB/ADOCE is not contemplated to be directy supported in the compact
framework.

Any though is greatelly appreciated!!!

Tarh Ik
 
Simple to answer. Assumption #1 is incorrect. ADODB is not supported in
the CF
 
Chris Tacke said:
Simple to answer. Assumption #1 is incorrect. ADODB is not supported in
the CF
Click to expand...

Hi Chris!!!

Thanks for your feedback. I know that ADODB is not supported... but I
made it work (kind of), as explained in my posting.

Thanks anyway!

Tark Ik
 
Let me give you an example of the type of comments that I'm looking for:

* Example1: Programming with the SQLCE should be better since this API
allows compiling queries that can be used many times by just changing the
value of its parameters, hence improving its performance.

* Example2: Programming with ADODB should be better since it is very
important not to marry to a single RDBMS. Instead, it is good to offer a
solution that will best embrace the technolgoy and know-how of the client
that requested the solution.

Thanks!!!

Tark ik
 
Tarh ik said:
Let me give you an example of the type of comments that I'm looking for:

* Example1: Programming with the SQLCE should be better since this API
allows compiling queries that can be used many times by just changing the
value of its parameters, hence improving its performance.

* Example2: Programming with ADODB should be better since it is very
important not to marry to a single RDBMS. Instead, it is good to offer a
solution that will best embrace the technolgoy and know-how of the client
that requested the solution.
Click to expand...

Well, taken the cirumstances (ADO not supported in the CF), then your
Example 2 should read:

* Example 2: Programming with ADOCE should be better as you just need to
write your own ADO wrapper system around quite a lot of unmanaged code,
which performs worse than SQLCE, and only caters for .CDB databases as there
are no 3rd party database systems for the WindowsCE platform. etc. etc.

I'm sorry, but that's not the way it is.
As Chris says, ADO usage in the .NET CF is discouraged and shouldn't be
pursued.

If your question had been:

"What's the best way to go for an all'round, easy-portable .NET database
accessing system.", then you might have yielded another (possibly better)
answer.

/Keld Laursen

PS: My apologies to Peter Foot for not mentioning his ADOCE wrapper for .NET
and to 47' floor for not making a plug for their database system.
;)
 
Hi Keld!!!

Thanks for your feedback!!! I already have my own wrapper routines. I
also have in mind a scenario in which I could use ADOCE with CF2 & COM.
However, after reading your comment I think that I better stop wandering
around and marry my new applications to SQLCE. After all, if everybody else
is doing the same, then that's what I should do. It is not good to stay
behind: it is way too expensive!!!! ;)

Best Regards,

Tarh Ik.
 
"Not supported" implies that you shouldn't bet on being able to get it to
work in future generations of devices.

--
Robert Levy
Program Manager
Mobile Devices Product Group
http://blogs.msdn.com/windowsmobile

This posting is provided "AS IS" with no warranties, and confers no
rights.
 
Hi Robert!!!

Thanks for your feedback. Wether I can make it work or not, I think I
should follow your advice since it seems that it is best practice to use what
I'm supposed to use. I don't like marrying myself with SQLCE, but hey, I must
admint that it is the best RDBMS so far for WinCE & PPC.

Thanks!!

Tarh ik
 
Back
Top