Re: ODBC Connection to SQL Server Compact

Tech-Archive recommends: Fix windows errors by optimizing your registry

Sorry for the delay but I have to reinstall my machine these last days.

I have no idea what's going wrong. It's your problem only with inserting
new records from ADO or if you can't read any record from the database as
well?

I will try some test this weekend but as I don't have the save version as
you (I have the 3.5), I'm not sure if I will be able to reproduce your
problem. Last time I checked, I don't remember having any problem using
this OLEDB driver from VBA.

--
Sylvain Lafontaine, ing.
MVP - Windows Live Platform
Email: sylvain aei ca (fill the blanks, no spam please)
Independent consultant and remote programming for Access and SQL-Server
(French)


"Spiros" <Spiros@xxxxxxxxxxxxxxxxxxxxxxxxx> wrote in message
news:6BEF0C2C-39B0-4344-93BE-4890E5259ACC@xxxxxxxxxxxxxxxx
Thanks again...I tried both options:
1) Use only 'execute' commands from con objet with no Rs (recordset) used.
2) Use only Rs recordset without using any commands from con object...
Both of them failded to add a new record on the remote database...What is
going wrong?

Regards,
Spiros.


"Sylvain Lafontaine" wrote:

Possibly because you are trying to use two open recordset on the same
connection object. A connection object must be used with a single
recordset
at a time and any previous recordset that has used this connection must
have
been closed before opening a new one.

--
Sylvain Lafontaine, ing.
MVP - Windows Live Platform
Email: sylvain aei ca (fill the blanks, no spam please)
Independent consultant and remote programming for Access and SQL-Server
(French)


"Spiros" <Spiros@xxxxxxxxxxxxxxxxxxxxxxxxx> wrote in message
news:04EBD58C-A65E-473A-9CC2-733680D80BE8@xxxxxxxxxxxxxxxx

Hi Sylvain,
I have tried all the possibilities...but with no luck so far..
1)First the "conn" object opens giving no errors in the error
collection..
2)Secondly the RS recordset opens nicely but when I try to access the
objects (RS(0), RS(1)...) I get an error message "Run time error
'3265'.
Item
not found in the collection...
Finally I thought to use the Conn.Execute "SqlStr" statement where
SqlStr
is
"INSERT INTO StockItems (ItemCode, OnBoxCode, FactoryCode, Description)
VALUES (1, '14158-001', '8431319393071', 'Antik Negro/Tee Marron')". I
tried
as query in SQL Management Studio and it worked fine and added a new
record
in the table "StockItems" of the Apog.sdf....BUT it does not work from
Access...
I think this piece of code is making fun of me...
Any ideas?
Thank you for your time again.
Kind Regards,
Spiros.


"Sylvain Lafontaine" wrote:

First, make sure that the RS is not empty. Second, print the name of
each
field of the RS recordset (and their other properties as well, too) by
using
their numerical index (Rs(0), Rs(1), ...). With that, probably that
you
should be able to see what's wrong.

--
Sylvain Lafontaine, ing.
MVP - Windows Live Platform
Email: sylvain aei ca (fill the blanks, no spam please)
Independent consultant and remote programming for Access and
SQL-Server
(French)


"Spiros" <Spiros@xxxxxxxxxxxxxxxxxxxxxxxxx> wrote in message
news:C9218E72-2B2C-437C-BE3D-BA4B141CB0F0@xxxxxxxxxxxxxxxx
Hi,
Thanks for the code again I did try it, and I found out the
following...
1)By using the connection string "Conn.ConnectionString =
"PROVIDER=Microsoft.SQLSERVER.CE.OLEDB.3.5;Data
Source=C:\\Apog\Apog.sdf"

I got Error Message: "The database file has been created by an
earlier
version of SQL Server Compact. Please upgrade using
SqlCeEngine.Upgrade()
method. [,,,,,]"

2)By using the connection string
"Conn.ConnectionString =
"PROVIDER=Microsoft.SQLSERVER.MOBILE.OLEDB.3.0;Data
Source=C:\Apog\Apog.sdf"

The conn object opened "nicely". But Rs recordset failed to
recognise
the
fields name (of the table) on the Apog database.
On Debugging Mode the Expression Rs![ItemCode]= LclRs("ItemCode")
the
field
"ItemCode" of Rs recordset was not updated and putting the cursor
the
msg
"Item not found in the collection..." Following that I checked the
Field
name
of the "StockItems" table in the Apog.sdf (using SQL Management
Studio)
but
I did not find any mistakes (mispellening etc..)
Any clues? (The code follows...)
Thank you in advance..
Kind Regards...
Spiros.

Sub SyncStockItems()

Dim Conn As ADODB.Connection
Dim Rs As ADODB.Recordset
Dim LclRs As ADODB.Recordset
Dim SqlStr, MsgStr As String
Dim RecsNo As Integer, LclRecsNo As Integer

On Error Resume Next

Set Conn = New ADODB.Connection
Set Rs = New ADODB.Recordset
Set LclRs = New ADODB.Recordset

LclRs.Open "StockItems", CurrentProject.Connection, adOpenKeyset,
adLockOptimistic
LclRecsNo = LclRs.RecordCount

'Microsoft.SQLSERVER.CE.OLEDB.3.5
'Conn.ConnectionString =
"PROVIDER=Microsoft.SQLSERVER.CE.OLEDB.3.5;Data
Source=C:\\Apog\Apog.sdf"
Conn.ConnectionString =
"PROVIDER=Microsoft.SQLSERVER.MOBILE.OLEDB.3.0;Data
Source=C:\Apog\Apog.sdf"



Conn.Errors.Clear
Conn.Open
'SqlStr = "SELECT StockItems.* FROM StockItems;"
'LclRs.Open SqlStr, CurrentProject.Connection, adOpenKeyset,
adLockOptimistic

If (Conn.Errors.Count > 0) Then
Dim e As ADODB.Error

For Each e In Conn.Errors
Debug.Print e.Description
Next
End If

On Error Resume Next

If (Conn.State = 1) Then

While Not Rs.EOF
Debug.Print Rs(0) & ": " & Rs(1)
Rs.MoveNext
Wend
End If


If (Conn.State = 1) Then
MsgBox "On ferme...."
Conn.Close
End If

Conn.Open

'Delete All Records from Mobile Database
RetVal = SysCmd(acSysCmdSetStatus, "Deleting Records from Mobile
Database....")
Conn.Execute "DELETE * FROM StockItems"
'Conn.
RetVal = SysCmd(acSysCmdSetStatus, "Records Deleted from Mobile
Database.")
Rs.Open "StockItems", Conn, adOpenForwardOnly, adLockOptimistic

'Delete All Records from Mobile Database
'Rs.Open "Delete * from StockItems", Conn

'Start Copying from Local Database to Mobile Database
LclRs.MoveFirst
RetVal = SysCmd(acSysCmdSetStatus, "Commencing Copy of Stock Items
Records
to Mobile Database.")
I = 1
While I <= LclRecsNo
Rs.AddNew
Rs![ItemCode] = LclRs("ItemCode")
Rs![OnBoxCode] = LclRs("OnBoxCode")
Rs![FactoryCode] = LclRs("FactoryCode")
Rs![Description] = LclRs("Description")
Rs.Update
RecsNo = Rs.RecordCount
'Debug.Print Rs(0) & ": " & LclRs(0)
'Debug.Print Rs(1)
MsgStr = "Record " & I & " of " & LclRecsNo & "."
RetVal = SysCmd(acSysCmdSetStatus, MsgStr)
I = I + 1
LclRs.MoveNext
Wend

LclRs.Close
Rs.Close
Conn.Close

Set Rs = Nothing
Set Conn = Nothing
Set LclRs = Nothing

End Sub


"Sylvain Lafontaine" wrote:

Did you try to take a look at the messages in the Errors collection
returned
by the Connection object as sugested?

--
Sylvain Lafontaine, ing.
MVP - Technologies Virtual-PC
E-mail: sylvain aei ca (fill the blanks, no spam please)


"Spiros" <Spiros@xxxxxxxxxxxxxxxxxxxxxxxxx> wrote in message
news:BEEB5F86-C20B-45B2-8688-D92BCB768D91@xxxxxxxxxxxxxxxx
Dear Sylvain,
Thanks for your time to deal with my problem and your
suggestions.
As
far
as
the password is concerned I am sure that is no need for that
since
when
I
am
opening the sdf file from SQL Management Studio...no username or
password
is
required to connect to database. I also make sure, when I am
running
the
Access code, that no other programs concerning SQL files is
running.
On
the
other hand I am not sure if any programs are running as
"services"
that
could
create sharing violation. I would like your suggestions on that
if
you
please...I will get back to you also when I try the rest of your
suggestions.
Thank you in advance.
Spiros Kostopoulos.

"Sylvain Lafontaine" wrote:

Your code looks fine, it's possible that you have a permission
problem -
for
example, a password is required - or that the database is
already
opened
in
exclusive mode by another problem, for example either SSMS or
VS.NET
if
you
are using one of these programs to create the SDF database file.

First, make sure that you have setup a reference to the
Microsoft
ActiveX
Data Objects 2.1 Library or later in the References dialog
window
of
VBA.

Second, take a look at the errors collection returned by the
connection
object; for example:

Dim conn As ADODB.Connection
Dim rs As ADODB.Recordset

Set conn = New ADODB.Connection
Set rs = New ADODB.Recordset

conn.ConnectionString =
"Provider=Microsoft.SQLSERVER.CE.OLEDB.3.5" _
& "Data Source=C:\Apog\Apog.sdf;"

On Error Resume Next

conn.Errors.Clear
conn.Open

If (conn.Errors.Count > 0) Then
Dim e As ADODB.Error

For Each e In conn.Errors
Debug.Print e.Description
Next

Exit Sub
End If

On Error Resume Next

If (conn.State = 1) Then
rs.Open "Select * from Table1", conn

While Not rs.EOF
Debug.Print rs(0) & ": " & rs(1)
rs.MoveNext
Wend

End If


.

Relevant Pages

  • Re: ODBC Connection to SQL Server Compact
    ... Sylvain Lafontaine, ing. ... "The database file has been created by an earlier ... The conn object opened "nicely". ... Dim Conn As ADODB.Connection ...
    (microsoft.public.access.modulesdaovba)
  • Re: OLEDB Connection to SQL Server Compact
    ... A connection object must be used with a single recordset ... Sylvain Lafontaine, ing. ... 1)First the "conn" object opens giving no errors in the error collection.. ...
    (microsoft.public.access.modulesdaovba)
  • Re: ODBC Connection to SQL Server Compact
    ... Possibly because you are trying to use two open recordset on the same ... A connection object must be used with a single recordset ... Sylvain Lafontaine, ing. ... 1)First the "conn" object opens giving no errors in the error collection.. ...
    (microsoft.public.access.modulesdaovba)
  • Re: ODBC Connection to SQL Server Compact
    ... 1)First the "conn" object opens giving no errors in the error collection.. ... Sylvain Lafontaine, ing. ... "The database file has been created by an earlier ... Dim Conn As ADODB.Connection ...
    (microsoft.public.access.modulesdaovba)
  • Re: Proper Database Connection Cleanup
    ... When I am done with a recordset I use the Close method. ... I use the Close method of the Recordset and Connection objects. ... What I want to do is have a function to open the database in an include ... Public Sub ConnectToDB2(byref XCmd, byref YRS, byRef Conn) ...
    (microsoft.public.scripting.vbscript)