Re: OLEDB Error

Erik,

I just reread your message and see you are trying to access SQL Compact from Visual Objects. If you don't also have Visual Studio installed on the computer, I assume that is why you are seeing that the key is missing.

Ginny

"E®!k \/!sser" <nospam@xxxxxxxxxx> wrote in message news:ucqCg3yvIHA.3760@xxxxxxxxxxxxxxxxxxxxxxx
Hi Ginny,

Perhaps you have added this key in the past yourself?
If I remove the complete key and repait the SqlCE installation, the OLE DB Provider-entry it is not added.

It is a 'known' issue:
For the previous version:
http://groups.google.com/group/microsoft.public.sqlserver.ce/browse_thread/thread/239c0b4bc6af8e6/8894f7eeabff88a6?lnk=st&q=oledb+erik+registry#8894f7eeabff88a6

and for the current:"
http://coding.derkeiler.com/Archive/Delphi/borland.public.delphi.database.ado/2008-02/msg00075.html
If you have this VO code:
LOCAL oConn AS AdoConnection
oConn := AdoDriverSelect(SELF)
oConn:Open(NIL,NIL,NIL,NIL)

You'll get the Datalink Property dialog with list of installed Ado/OleDBProviders. To have the SQL CE provider listed here, it is neccesary
to add this key. This problem was there in the 3.0 version and in the current.

Erik








"Ginny Caughey MVP" <ginny.caughey.online@xxxxxxxxxxxxxx> schreef in bericht
news:CDA7F694-B3D6-49F1-8633-0ACC77AD5E04@xxxxxxxxxxxxxxxx
Hi Erik,

I seem to already have that registry key in my registry. What does adding
it do for you? By the way, the OleDb support in SQL Compact doesn't
implement the full OleDb standard so I suspect that is why you don't see
the same wizard behavior you get with other providers.

Ginny

"E®!k \/!sser" <nospam@xxxxxxxxxx> wrote in message
news:%23X%23FxukvIHA.5584@xxxxxxxxxxxxxxxxxxxxxxx
Hi Ginny,

Downloaded the SP1 beta, installed, tested and... no luck.
I can update a nVarchar column > 127 without problems, but a query that
include this column fails.

Also the SQLCE OleDB provider does not show up in the listed OleDB
provider on the Datalink wizard window.
Still needs a manual patch in the registry to 'see' the provider.

this key needs to be added:
[HKEY_CLASSES_ROOT\CLSID\{F49C559D-E9E5-467C-8C18-3326AAE4EBCC}\OLE DB
Provider]
@="SQL CE OleDB Provider"

Erik





"Ginny Caughey MVP" <ginny.caughey.online@xxxxxxxxxxxxxx> schreef in
bericht news:E21958C6-3B73-407D-A58F-2FF3BD2FCC6B@xxxxxxxxxxxxxxxx
Hi Erik,

Have you tried this again with the SQL Compact sp1 beta?
http://www.microsoft.com/downloads/details.aspx?FamilyId=68539FAE-CF03-4C3B-AEDA-769CC205FE5F&displaylang=en

Ginny Caughey
Device Application Development MVP

"E®!k \/!sser" <nospam@xxxxxxxxxx> wrote in message
news:%23kLz06ZvIHA.5288@xxxxxxxxxxxxxxxxxxxxxxx
Stepan,

This is a bug. I ran into this 18 months ago or so, sorry to see this
is still not fixed.
See the discussion
http://groups.google.com/group/microsoft.public.sqlserver.ce/browse_thread/thread/93ae1aded52d6020/3d6f1b571ff3a0e2?lnk=gst&q=128+erik#3d6f1b571ff3a0e2

regards,

Erik



"StepanM" <stepmikhaylov@xxxxxxxxx> schreef in bericht
news:a253aee7-4e69-465b-a692-38026a9538ea@xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
I'm accessing SQL Compact 3.5 database using OLEDB provider.

pConnection->Open(L"Provider=Microsoft.SQLSERVER.CE.OLEDB.3.5;Data
Source=c:\\db.sdf;Persist Security Info=False", L"", L"", -1)

I'm trying to execute simple "select" query.

_RecordsetPtr pRS(__uuidof(Recordset));
HRESULT hr = S_OK;
hr = pRS->raw_Open(_variant_t(L"SELECT [Table_1].[Field_1] FROM
[Table_1]"), _variant_t(pConnection), adOpenDynamic, adLockOptimistic,
adCmdText);

But an error (hr = DB_E_ERRORSOCCURRED) is returned if [Table_1].
[Field_1] has type nvarchar(128 or more).

There is no error if [Table_1].[Field_1] has type nvarchar(127 or
less).

How can I resolve this problem?

Thanks






.

Relevant Pages

  • Re: OLEDB Error
    ... I am able to use the Add Data Source and Add Connection wizards in VS to add a SQL Compact database as a data source, for example, or are you referring to some other functionality you get by adding this registry key yourself? ... I assume that by removing the key and then repairing the SQL Compact installation not fixing it, that VS installs that key so perhaps a repair of VS might return it after it's removed. ... the OleDb support in SQL Compact doesn't ... Also the SQLCE OleDB provider does not show up in the listed OleDB ...
    (microsoft.public.sqlserver.ce)
  • Re: OLEDB Error
    ... If I remove the complete key and repait the SqlCE installation, the OLE DB Provider-entry it is not added. ... the OleDb support in SQL Compact doesn't ... Also the SQLCE OleDB provider does not show up in the listed OleDB ... Have you tried this again with the SQL Compact sp1 beta? ...
    (microsoft.public.sqlserver.ce)
  • Re: ADO connection with VBS to locally stored MS-Access database
    ... MDAC 2.8 installation so far contains OLEDB Provider for ODBC, ...
    (microsoft.public.data.ado)
  • Re: TSP is not getting Started after installation
    ... delete the provider and add it again using manage providers, ... Is TSPI_providerInstallcalled during installation? ... TAPI / TSP Developer and Tester ... resolved after adding the provider through control panel. ...
    (microsoft.public.win32.programmer.tapi)
  • Re: TSP is not getting Started after installation
    ... delete the provider and add it again using manage providers, ... Is TSPI_providerInstallcalled during installation? ... TAPI / TSP Developer and Tester ... resolved after adding the provider through control panel. ...
    (microsoft.public.win32.programmer.tapi)
Loading