Re: Micosoft Contradiction regarding ADOCE and C++
From: PKNET (PKNET_at_discussions.microsoft.com)
Date: 08/08/04
- Previous message: Troy: "Re: Micosoft Contradiction regarding ADOCE and C++"
- In reply to: Troy: "Re: Micosoft Contradiction regarding ADOCE and C++"
- Next in thread: Joćo Paulo Figueira [eMVP]: "Re: Micosoft Contradiction regarding ADOCE and C++"
- Reply: Joćo Paulo Figueira [eMVP]: "Re: Micosoft Contradiction regarding ADOCE and C++"
- Reply: Chris Tacke, eMVP: "Re: Micosoft Contradiction regarding ADOCE and C++"
- Messages sorted by: [ date ] [ thread ]
Date: Sat, 7 Aug 2004 18:25:01 -0700
Troy - thanks for your thoughts and recommendations. I appreciate hearing
from other developers who have fought their own up hill battles. I have
spent 90% of my development time searching for a valid solution and still
having difficulty in finding answers with regards to WinCE 4.x with ADOCE and
C++.
There is a clarification I would like to make based on your response.
Most people who have ever responded to any of my previous questions
regarding this matter have alway misunderstood that somehow SQL Server CE is
involved in our project, it is not. We do not install SQL Server CE on our
CE device or care that it even exists. We are attempting to have our Windows
CE 4.x device communicate with a remote (non-local) SQL Server 2000 (not SQL
Server CE!) via ADOCE and a third party OLE DB provider suggested by
Microsoft to call stored procedures. Our tables, stored procedures, etc.
can never be stored or replicated on the Windows CE devices. We simply
desire to execute stored procedures on a remote SQL Server 2000 from a CE
device using ADO. This is the current standard for all non-CE based
applications!
It is bizarre that Microsoft has not laid out a clear development path for
Windows CE devices to connect to the huge number of existing SQL Server 2000
installations via ADO and an OLE DB provider. This is the standard for all
existing ADO based applications communicating to SQL Server 2000 running on
Win2K. Microsoft fails to provide an OLE DB provider for Windows CE devices
at all and refers you to another company which charges a high per unit
license fee. Windows CE devices are attractive solution for many
corporations partly because of the low cost per unit. By not providing an
OLE DB provider, Microsoft defeats itself and fails the developers.
Finally, it is even more bizarre that Microsoft contradicts itself regarding
C/C++ development with ADOCE. What serious C/C++ developer is going to say
well gee let's code this important project in candy ass Visual Basic because
it offers an ADOCE control!? I wish Bill Gates would get off of the idea of
making programming viable for the average household mother. Everyone I have
spoken to regarding our Windows CE ADOCE issues advises us to switch to Linux
but I have a long standing history with Microsoft development products and
refuse to give it up.
Another major issue I have with Microsoft is that they convoluted native
C/C++ development with .NET compact framework manged code. It has become
difficult to weed all that stuff out in order to get back what use to be the
standard C/C++ Win32 API method of coding. On top of all that, Microsoft
decides to invent C#! Now, I would move to the newer technolgoies for our
project but there are holes and missing components. For instance, our
Windows CE application is DirectDraw based which the CE .NET compact
framework stuff does not handle.
We desire to use ADOCE from a Windows CE 4.x device in conjuction with a
third party OLE DB provider (as suggested by Microsoft) to communicate to a
REMOTE (non-local) SQL Server 2000 to call stored procedures from a native
C/C++ WinCE 4.x application.
The problem: Microsoft claims it can and can't be done! Microsoft fails to
provide OLE DB and suggests an expensive per unit third party option!
Microsoft does not offer a clear development path for native C/C++ CE
applications!
Any additional help or information in clearing up these issues is greatly
appreciated.
.....
"Troy" wrote:
> Well, it just really means that adoce support for C++ really blows. I
> mean they initially want you to use a set of wrapper classes from
> virtual office systems which I used in my first couple of programs. It
> got the job done, but since I was going up against pocket access and all
> its limitations, (i.e. no sum, count, unique statements). I really
> hated it. I would however whole heartedly recommend the classes from
> Joao Figueira. His classes made the switch for me over to SQL Server CE
> easy, and the wrapper just feels very well made. The classes can be
> found at:
>
> http://www.codeproject.com/ce/ado_ce_ca.asp
>
> The line you will be looking in the class to set it to whatever database
> your are using is:
>
> provider=MyDataProvider;data source=\\name_of_data_base.???
>
> for example
> provider=Microsoft.SQLSERVER.OLEDB.CE.2.0;data source=\\db.sdf
>
> Hope this helps!
>
> Troy
>
>
> PKNET wrote:
> > Microsoft is clearly contradicting itself with regards to using ADOCE in C++.
> >
> > On the one hand, Microsoft claims ADOCE is only supported when called from
> > Visual Basic for Windows CE.
> >
> > On the other hand, Microsoft is providing MSDN support on how to implement
> > ADOCE from a pure C++ application with example code.
> >
> > Which is the truth?
> >
> > We desire to use ADOCE from a Windows CE 4.x device in conjuction with a
> > third party OLE DB provider (as suggested by Microsoft) to communicate to a
> > REMOTE (non-local) SQL Server from a native C/C++ WinCE 4.x application.
> > There are several hurdles to overcome. For instance, how to install ADOCE to
> > the CE device and how to call ADOCE from C++. In additon, why does Microsoft
> > force us to license a third party OLE DB provider -- why doen't Microsoft
> > provide its own version or purchase the technology from Oddessy (ViaDB).
> > Bill Gates is well aware of this company and has recommended it as a source
> > for COM based software. Oddessy wants big bucks per unit to license the OLE
> > DB provider and has a lock on the market.
> >
> > Below is is the evidence of Microsoft's contradictory stance on using ADOCE
> > with C++.
> >
> > "The Microsoft ActiveX Data Objects (ADO) for Windows CE 3.1 (ADOCE)
> > database technology is currently only supported when called from Visual Basic
> > for Windows CE."
> > http://support.microsoft.com/default.aspx?scid=kb;en-us;296395
> >
> > Using ADOCE with Pure C++ā¦
> > "Pocket PC devices come preloaded with ADOCE (Active Data Objects for the
> > WindowsĀ® CE operating system). This enables applications developers targeting
> > the Pocket PC to take advantage of a powerful database language that is well
> > established, well documented, and very robust. This article will show you how
> > to access ADOCE from a C++ application."
> > http://msdn.microsoft.com/library/default.asp?url=/library/en-us/dnppc2k/html/ppc_eplus.asp
> >
> > Now, I don't care if the ADOCE is an undocumented or not supported C++
> > feature. I just want to know that it is possible and how to implement it to
> > achieve the result I outlined above.
> >
> > Any addition help or information in clearing up this issue is greatly
> > appreciated.
> >
> > Thanks in advance....
> >
>
- Previous message: Troy: "Re: Micosoft Contradiction regarding ADOCE and C++"
- In reply to: Troy: "Re: Micosoft Contradiction regarding ADOCE and C++"
- Next in thread: Joćo Paulo Figueira [eMVP]: "Re: Micosoft Contradiction regarding ADOCE and C++"
- Reply: Joćo Paulo Figueira [eMVP]: "Re: Micosoft Contradiction regarding ADOCE and C++"
- Reply: Chris Tacke, eMVP: "Re: Micosoft Contradiction regarding ADOCE and C++"
- Messages sorted by: [ date ] [ thread ]
Relevant Pages
|