Write Variable to Table (Newbie needs some help)

[skotseno]

I am brand new to this forum and pretty new to access. I have everything working except I can't figure out how to get access VBA to write values to my table.

Table name: tblECN
Variable in table that I would like to write a value for: Customer

I have been scavenging the interweb in hopes of finding help with no avail so far. Here is my code:

Private Sub chkCustomerAff_Click()
Dim CustName As String
'Dim strSQL As String
'Dim db As DAO.Database
'Set db = CurrentDb
'Dim rstblECN As DAO.Recordset
Dim rstblECN As Object
'Set rstblECN = CurrentDb.OpenRecordset("Select * From Demographics Where False")
CustName = InputBox("Customer name: ", "Customer Name", "Customer")
If CustName <> "" And CustName <> "Customer" Then
lblCustomer.Caption = CustName
'strSQL="UPDATE tblECN SET Customer= '"&CustName&"' WHERE Customer=CustName"
With rstblECN
.Fields.Item("Customer") = CustName
End With
End If
End Sub

Sorry there are a lot of quoted out lines (I struggled with it for a while before giving up). Any help would be greatly appreciated.

[ranman256]

Use a query.
either append qry, or update qry.

[Bob Fitz]

If you must use a recordset you will need to use AddNew or Edit and complete with Update. See the following link point 6 Adding a Record:
http://www.utteraccess.com/wiki/inde...dding_a_Record

[Missinglinq]

I am brand new to this forum and pretty new to access

I cannot think of a worse way to learn about Access than using Unbound Forms! Using Unbound Forms does away with the main reason that developers choose to use Access, which is to take advantage of it ability to facilitate the RAD (Rapid Application Development) of Databases.

With Bound Forms, Access does the vast majority of the heavy lifting; with Unbound Forms the developer has to write code for just about everything, even the most mundane tasks. Several developers I know, experienced in Visual Basic database development, as well as Access development, estimate that development, using Unbound Forms, by highly experienced developers, takes two to three times as long, using Unbound Forms, as it does when using Access and Bound Forms.

In short, there is very little that can be done using Unbound Forms that cannot be accomplished with Bound Forms, and usually done with less work!

Anyone who insists on using Unbound Forms, would be far better off using a straight VB or C++ front end with a SQL Server or Oracle back end.

• You can create an EXE file which gives total protection to your code/design
  
• You can distribute the db to PCs without a copy of Access being on board
  
• Your data security is far, far better than anything you can do in Access

It should be added that there are a few very specialized reasons for using Unbound Forms in Access, for general data entry of Records, but they are very specialized, and situations that a newbie is very unlikely to come upon. I've been writing Access apps for well over a decade now, and have never had the need for using Unbound Forms for general data entry.

I applaud you efforts to learn Access, but you should first learn to use it as it is intended to be used, then you can move on to modifying its behavior, if the occasion arises.

Linq ;0)>

[skotseno]

If you must use a recordset you will need to use AddNew or Edit and complete with Update. See the following link point 6 Adding a Record:
http://www.utteraccess.com/wiki/inde...dding_a_Record

Thanks! I used this link as well as some frustration but got it! Big help

[Perceptus]

Using unbound forms and binding data to them is a something you may find documented in legacy applications. Lots of vb6 apps were made this way even though binding through the controls properties was available. Its not bad or good.

[skotseno]

Using unbound forms and binding data to them is a something you may find documented in legacy applications. Lots of vb6 apps were made this way even though binding through the controls properties was available. Its not bad or good.

I'm not sure why I keep getting messages about using unbound forms because that's not what I was doing. I was using a check box that triggered a input box to change the caption for the check box label. If the caption was changed, then I recorded the new caption in a table.