Open and update a SQL table

[Bruce Lawrence]

I have a table on a SQL server called history. When I link this table
using an ODBC connection, i give it the username and password and tell
it to save the password and it works great. On my PC. Other computers
however get asked for the password each time they try to write records
to the table.

What I'm trying to do is remove the linked table and open the SQL
database in a module and use the INSERT INTO query to insert my records
and then close the DB connection.

Is this the best way to do this? Can someone provide me some sample
code that will open a SQL database using ODBC and then insert some
records into a history table and then close it all down?

I'm using Access97 and SQL 2000.

Thanks !

[Justin Hoffman]

"Bruce Lawrence" <dg*********@ho tmail.com> wrote in message
news:11******** *************@g 43g2000cwa.goog legroups.com...

I have a table on a SQL server called history. When I link this table
using an ODBC connection, i give it the username and password and tell
it to save the password and it works great. On my PC. Other computers
however get asked for the password each time they try to write records
to the table.

What I'm trying to do is remove the linked table and open the SQL
database in a module and use the INSERT INTO query to insert my records
and then close the DB connection.

Is this the best way to do this? Can someone provide me some sample
code that will open a SQL database using ODBC and then insert some
records into a history table and then close it all down?

I'm using Access97 and SQL 2000.

Thanks !

How is the SQL Server set up? With Windows/Built-in/Integrated security
only or does it allow SQL authentication - and which do you use? It makes
it easier for you if it's Windows authentication only since you don't have
to worry about storing passwords, but if you use SQL authentication what do
you feel about passwords and security? Should people log in each time - or
could a password be stored?
Finally have you considered ADO for this if there is no real need to have
linked tables - just an application which does inserts.

[Bruce Lawrence]

I'm using SQL authentication. The login name is "mplrpt" and there is
no password.
The password could be stored. I'd rather not link the table in Access.
I'd rather open the DB in VB code and insert the records directly.

I'm not sure really about ADO or how it would work in this instance.
All I'm doing now is sifting through sample code in Access and trying
to adjust it to my needs but its not working heh.

[Justin Hoffman]

"Bruce Lawrence" <dg*********@ho tmail.com> wrote in message
news:11******** **************@ g49g2000cwa.goo glegroups.com.. .

I'm using SQL authentication. The login name is "mplrpt" and there is
no password.
The password could be stored. I'd rather not link the table in Access.
I'd rather open the DB in VB code and insert the records directly.

I'm not sure really about ADO or how it would work in this instance.
All I'm doing now is sifting through sample code in Access and trying
to adjust it to my needs but its not working heh.

Well you could try this sort of approach (which uses late binding to avoid
mentioning references)

Private Sub ADO_ADD()

On Error GoTo Err_Handler

Dim cnn As Object
Dim strCnn As String
Dim strSQL As String
Dim lngRecords As Long

strCnn = "Provider=sqlol edb;" & _
"Data Source=MyServer ;" & _
"Initial Catalog=MyDatab ase;" & _
"User ID=mplrpt;Passw ord=;"

Set cnn = CreateObject("A DODB.Connection ")

cnn.ConnectionS tring = strCnn

cnn.Open

strSQL = "INSERT INTO tblTest (MyText, MyNumber) VALUES ('Hello', 22)"

cnn.Execute strSQL, lngRecords

MsgBox lngRecords & " record(s) added", vbInformation

Exit_Handler:

If Not cnn Is Nothing Then
cnn.Close
Set cnn = Nothing
End If

Exit Sub

Err_Handler:
MsgBox Err.Description , vbExclamation, "Error No: " & Err.Number
Resume Exit_Handler

End Sub

[Bruce Lawrence]

Awesome !

Without going into great detail, can you explain the difference between
what you posted and this:

Set mplwksp = CreateWorkspace (blah blah)
Set mplhistory = mplwksp.OpenDat abase (blah blah)

Thank you so much !

[Bruce Lawrence]

Well, slight problem just came up...

When I changed your SQL statement to mine, I get an error

Line1: Incorrect Syntax near ","

This is my statement
SQLstr = "INSERT INTO history
(clockno,job,em pname,ordno,cur date,machno) VALUES" & _
"('" & Packer & "','Packer' ," & packname & "," & order & "," &
Now() & "," & machno & ")"

[Justin Hoffman]

"Bruce Lawrence" <dg*********@ho tmail.com> wrote in message
news:11******** **************@ z14g2000cwz.goo glegroups.com.. .

Well, slight problem just came up...

When I changed your SQL statement to mine, I get an error

Line1: Incorrect Syntax near ","

This is my statement
SQLstr = "INSERT INTO history
(clockno,job,em pname,ordno,cur date,machno) VALUES" & _
"('" & Packer & "','Packer' ," & packname & "," & order & "," &
Now() & "," & machno & ")"

Do a debug.print SQL and the problem should become clear. It will be quotes
or similar. For the dates use
'2005-12-25' format

[Bruce Lawrence]

Thanks for the reply Justin

The way I fixed it was this:

curdate = Now()

I also made sure my datatype on the SQL server matched the format and
its working great now !

Thanks for all the help. You saved me tons of work