Hi

I am currently trying to build a case management database which involves
students and different areas of interest: Presecreening, Pre-entry, surveys
at 6 month intervals, current information, health needs, mental needs, risk
factors, care, treatment, etc.

I was a bit thrown off when some NotInList events sorted and some didn't.
They are all using the same code. Each time I copied the events I made the
necessary changes.

This is the code I used for the NotInEvent procedure for adding a new
hometown:

Private Sub Hometown_NotInList(NewData As String, Response As Integer)

On Error GoTo Insert_Error
intAnswer = MsgBox("This city is not currently in the list." & vbCrLf & _
"Would you like to add this city to the list now?" _
, vbQuestion + vbYesNo, "This city")

If intAnswer = vbYes Then
strSQL = "INSERT INTO CB_City([City]) " & _
"VALUES ('" & NewData & "');"
DoCmd.SetWarnings False
CurrentDb.Execute strSQL, dbFailOnError
DoCmd.SetWarnings True
MsgBox "This city has been added to the list." _
, vbInformation, "NewData"
Response = acDataErrAdded
End If
Exit Sub

Insert_Error:
MsgBox "The attempted insert produced the following error:" & vbCrLf & Err
Response = acDataErrContinue
End Sub

The changes I would make is to the message box statement and the table and
field name.

Thanks

"John W. Vinson" wrote:

On Thu, 25 Mar 2010 20:22:01 -0700, forest8
wrote:

Hi

I have created about 30 NotInList events in my database.

Is it better to have 30 individual requeries or 1 requery that contains all
of them?

Thank you

None.

A properly written NotInList event will automatically requery the combo box to
which it is attached, and unless you're doing something really strange, no
other query or object should be affected.

Please explain a bit more about what sounds like a really strange form!
--

John W. Vinson [MVP]
.