• I have an old app that has ADOCE 3.1 Header files:

    adoce31.h, many other files named adoce31: idl, tlb; etc, as well as oledb.h and oledb26x.h.

    In my SQL Compact 3.5 SP1 directory, include directory, I only have the oledb stuff:

    C:\>dir "c:\Program Files\Microsoft SQL Server Compact Edition\v3.5\Include"
     Volume in drive C has no label.
     Volume Serial Number is 3CF6-5B57

     Directory of c:\Program Files\Microsoft SQL Server Compact Edition\v3.5\Include

    08/27/2008  08:53 AM    <DIR>          .
    08/27/2008  08:53 AM    <DIR>          ..
    05/14/2008  02:28 PM           143,144 sqlce_err.h
    05/14/2008  02:28 PM           567,433 sqlce_oledb.h
    10/08/2007  12:08 PM           137,573 sqlce_sync.h
                   3 File(s)        848,150 bytes

    Is there ADOCE headers for SQL Compact 3.5?


    Tuesday, November 17, 2009 3:16 PM


All replies

  • ADOCE is no longer a supported technology. Neither is SQL CE 2.0 Erik Ejlskov Jensen - Please mark as answer, if this was it.
    Tuesday, November 17, 2009 8:05 PM
  • So using raw OLEDB with SQL Compact 3.5 is supported, but using ADOCE is not?

    It works fine using the ADOCE 3.1 headers + the SQL Compact 3.5 OLEDB Provider.

    What is Microsoft's native code story for SQL Compact 3.5?
    Wednesday, November 18, 2009 4:23 AM
  • The "story" is OLE DB and C++ - Erik Ejlskov Jensen - Please mark as answer, if this was it.
    • Marked as answer by tballard Wednesday, November 18, 2009 2:22 PM
    Wednesday, November 18, 2009 5:37 AM
  • Since ADO is a higher level abstraction that works (in theory) with any proper OLEB provider, then there shouldn't be anything wrong with using the ADOCE 3.1 headers and the SQL Compact 3.5 OLEDB Provider, as long as both runtime are installed.

    Wednesday, November 18, 2009 2:24 PM