I appreciate your response.
OK...
Main client form:
Combo box to select client's record of choice.
When not in list, OnNotInList queries user if they want to add as new client.
Affirmative response opens a client entry form.
When information complete the user closes the new client entry form via
button.
Now we are back at the main client form with a complete new client record in
the table. The main form at this point remains on the last client record
selected.
Viewing the list in the combo box reveals the new client is present.
First attempt with added new client:
Selecting that new client at that point does nothing.
Second attempt, freshly added new client:
Selecting any other client first, then selecting the new client results in
the form returning the first record in the table.
Third attempt, another freshly added new client;
Closing the main form, reopening it, then selecting the new client works
correctly.
That's why I think its a requery/refresh, combo box or form issue.
Trying requery the combo box in several places (one at a time) results in
error message 2118, save first. Then I get really lost.
Does that help you to help me?

Signature
Thanks for your help,
Chris
A somewhat longish thread dealt with exact same issue.
Contents of which betwix *** <Q> *** and *** <UNQ> ***
*** <Q> ***
In yr Client entry form, you use this line:
>> > If Me.Dirty Then Me.Dirty = False
Why do you need this line?
The Client entry form is opened in an acAdd state. If you undo the changes,
the new record isn't saved.
What happens if you leave out this line?
If the above suggestion fails,
here's a slightly different approach; try to implement
[mainform code)
NotInList() event of the combo fires:
Write the new record to the table
Make sure changes are committed
Pickup the ID of the new record
Set the Response parameter to acDataErrAdded
Open the Client Entry form normally, use a filter or a where statement
using the ID
[frm 1 Client entry code]
Let the user do the entry of other client info on the form, don't toggle
the Dirty() property!~
While having a pointer to your mainform (still loaded I presume), you
may need to requery the combo on yr mainform
Set the combo value (on mainform) to the ID you used previously
Close the Client entry form and your back in the mainform with the new
record selected in the combo
--
Krgrds,
Perry
System:
Vista/Office Ultimate
VS2005/VSTO2005 SE
"Chris" <Chris@discussions.microsoft.com> schreef in bericht
news:9FA1C054-D3A9-48BF-9C9E-ED1CC335E34D@microsoft.com...
> Thanks for responding.
>
[quoted text clipped - 110 lines]
>> >
>> > End Sub
*** <UNQ> ***
--
Krgrds,
Perry
System:
Vista/Office Ultimate
VS2005/VSTO2005 SE
>I appreciate your response.
>
[quoted text clipped - 77 lines]
>> >
>> > I appreciate all help; especially the solution.
Chris - 22 May 2007 01:06 GMT
That would be your earlier suggestion in another post of mine to eliminate a
message appearing twice. As I responded to your last over at that message, I
used your suggestions and managed somehow to get to the point I am now --
unable to return to the new client record.
Granted, as an amateur I don't see things as readily. I have winnowed the
double-message issue to one of inability of the user to "land" on the new
client's record after all client data is entered.
I am unable to see this solution in the prior postings. If it is, in fact,
the same issue please explain it to me.
I appreciate your time and help.

Signature
Thanks for your help,
Chris
> A somewhat longish thread dealt with exact same issue.
> Contents of which betwix *** <Q> *** and *** <UNQ> ***
[quoted text clipped - 245 lines]
> >> >
> >> > I appreciate all help; especially the solution.
Perry - 22 May 2007 01:12 GMT
> unable to return to the new client record.
Important:
Let's get one thing straight: you've eliminated the duplicate warning and
you are now
stuck to the combo not presenting the correct (new) entry, right?
Pls confirm?
If so, could you kick in the new code you got, regarding bringing up the
Client Entry form
and the relevant code closing the Client Entry form?
--
Krgrds,
Perry
System:
Vista/Office Ultimate
VS2005/VSTO2005 SE
> That would be your earlier suggestion in another post of mine to eliminate
> a
[quoted text clipped - 280 lines]
>> >> >
>> >> > I appreciate all help; especially the solution.
Chris - 22 May 2007 01:58 GMT
Yes, I confirm that. The new client does appear in the combo box. I just
cannot do anything with it unless and until I close the form it is on and
reopen it. Then I can select the new client.
All I am trying to do is -- upon closing my detail entry form return to the
main form at the record of the new client. I have assumed because of the
aforementioned behavior that my issue was requery. I further assumed once I
understood why I could not requery the combo box without an error 2118 about
saving first that I would be able to load some code in the closing routine of
the detail entry form to select the new client's record for the main form.
Main client form not in list code:
Private Sub cboClient_NotInList(NewData As String, response As Integer)
Dim Result
Dim msg As String
Dim CR As String
CR = Chr$(13)
' Exit this subroutine if the combo box was cleared.
If NewData = "" Then Exit Sub
NewData = UCase(NewData)
' Ask the user if he or she wishes to add the new client.
msg = "'" & NewData & "' is not in the list." & CR & CR
msg = msg & "Do you want to add this new client?"
If MsgBox(msg, vbQuestion + vbYesNo + vbDefaultButton2) = vbYes Then
' If the user chose Yes, start the NewClient form in data entry mode
as a dialog form,
' passing the new client id in NewData to the OpenForm method's
OpenArgs argument. The
' OpenArgs argument is used in client form's Form_Load event
procedure.
DoCmd.OpenForm "frm1 ClientEntry", , , , acAdd, acDialog, NewData
End If
' Look for the client the user created in the NewClient form.
Result = DLookup("[ClientID]", "tbl 1 CLIENT", "[ClientID]='" & NewData & "'")
If IsNull(Result) Then
' If the client was not created, set the Response argument to
suppress an error
' message and undo changes.
response = acDataErrContinue
MsgBox "The client record WAS NOT created."
Else
' If the client was created, set the Response argument to indicate
that new data
' is being added.
response = acDataErrAdded
MsgBox "The client record WAS created"
End If
End Sub
Client entry form closing code (command button):
Private Sub btnCloseForm_Click()
DoCmd.Close
End Sub
I removed all the code from the closing button to start over; I was going in
twelve different directions.

Signature
Thanks for your help,
Chris
> > unable to return to the new client record.
>
[quoted text clipped - 253 lines]
> >> >
> >> > Does that help you to help me?
Chris - 22 May 2007 19:31 GMT
Thanks for the help. I've managed to get it done.

Signature
Thanks for your help,
Chris
> > unable to return to the new client record.
>
[quoted text clipped - 253 lines]
> >> >
> >> > Does that help you to help me?