Note that there are some explanatory texts on larger screens.

plurals
  1. PO
    text
    copied!<p>You have two options, you can either import the data into access or link the tables in access so the data stays in SQL CE and is just referenced by access.</p> <p>I don’t think access can import it directly so you will have to make an ODBC connection to your CE file using the ODNC admin program in windows. Once you have done that you can move onto the next step</p> <p>On the file menu go to get external data and then either import or link depending on what option you want, on the next dialog box select ODBC databases as the file type and select the ODBC connection you just made.</p> <p>Follow the on screen prompts from there and Roberts your mothers brother</p> <p>EDIT:</p> <p>Sorry yes I did mean ODBC, my finger must have slipped on the keyboard. Anyway Yes it looks like the ODBC driver does not exist however a OLEDB driver does so you could open up the database in code using ADO and either manipulate it there or loop through each table and insert it into an access table you created earlier. Here is some code showing how to open a SQL CE recordset in VBA</p> <pre><code>Sub test() Dim pConn As ADODB.Connection Dim pRS As ADODB.Recordset Set pConn = New ADODB.Connection Dim cmd As New ADODB.Command Set pRS = New ADODB.Recordset ' For 3.0 use PROVIDER=Microsoft.SQLSERVER.MOBILE.OLEDB.3.0 pConn.ConnectionString = "PROVIDER=Microsoft.SQLSERVER.CE.OLEDB.3.5;Data Source=C:\Northwind.sdf" pConn.Open cmd.ActiveConnection = pConn cmd.CommandText = "SELECT * FROM Products" Set pRS = cmd.Execute ' Open the recordset While Not pRS.EOF Debug.Print pRS(0) Debug.Print pRS(1) pRS.MoveNext Wend End Sub </code></pre>
 

Querying!

 
Guidance

SQuiL has stopped working due to an internal error.

If you are curious you may find further information in the browser console, which is accessible through the devtools (F12).

Reload