Use the Form's AfterUpdate Event

Me.Requery

-Raymond

Is the continuous form a subform in the current form or an external form completely?

Richard has several TechHelp videos on that go over Requery techniques so it is hard to guess which method you're referring to:

Refresh v Requery
Requery in Place
Requery Subform
Immediate Refresh

And many other videos that include requerying.

You could have your main form requery the continous form everytime you move to a new record. Or you could have it requery when you add or update any record. (and have the continuous form focus on the record you just added/updated if you want)

So need a little more context to help you find the best solution for your situation.

Thank you both for your response. I think Raymond's option may work but I tried just not doing something correct. Donald your first sentence explains exactly what I want to do. The form I am working in is not a subform it is a stand alone form that feeds the continuous form that is a stand alone also.

Then as Raymond said, it's as simple as placing the requery in the After Update of the entry form:

Private Sub Form_AfterUpdate()
     Forms!MyContinousForm.Requery
End Sub

Just Replace "MyContinuousForm" with the name of your form. Or, if the form name has spaces or other characters, you can do:

Forms("My Continuous Form").Requery

Thank you I will give that a try. Thanks so much guys I appreciate it.

Donald I tried both of those strings and it does not update the continuous form until I close it and re open it. I tried it on the entry form and continuous form

I figured it out, thank you very much. I did something wrong. I appreciate your help and patience.

Glad you got it figured out, Lee. Troubleshooting something like that yourself is one of the best ways to learn Access. The Form_AfterUpdate event on the entry form is the right place for it, assuming the continuous form is already open when the record is saved.

Richard I can say there's been a lot of help from a lot of people to get me where I am. John kept me interested when I was ready to give up early on for sure. Tell you that when I first tried Donald's strings he gave me I got frustrated, then I realized I was putting the name of the entry form in the string instead of the continuous form. Just little things like that get me in a bind. I think it may be old age, or not paying attention or both. But thank you to you all of the people that help and have patience.

Lee you're doing great. We all have our moments where nothing seems to work and then, out of the blue you find little things that seemed right at first and then if you take a breath, you can see it's not  exactly what you wanted

You're doing fine, Lee. That kind of thing happens to everyone, including me. You stare at it for an hour, walk away for five minutes, and suddenly the problem jumps right off the screen.

A lot of us coders are up until 3 in the morning goofing around with something, beating our heads against the wall. Then I go to sleep, and when I look at it fresh the next morning, the answer is obvious. I don't know what it is, but it happens all the time.

It's taken me 50 years of life to realize that when I get frustrated with a problem, I need to set it aside. Go take a walk, sleep on it, or sit in the throne room LOL (best ideas come here). The key is to put it out of your conscious mind for a little while. Your brain keeps background-processing it, and then you come back at it from a different angle.

And yes, using the name of the entry form instead of the continuous form is exactly the kind of tiny detail that can cause a big headache. The important part is that you found it and now understand why it works. That's progress, not old age.

Talking about strings, is there any video or where can i learn and understand the different parts of the string? For example I can have a double click event on one form to open a form and in the middle of the string I may have 2 commas and then I add a 3rd comma and it works fine and vice versa. I don't understand or know enough how to break it down or understand each part of it. I know Access will pop up options to assist you you but if you don't start off correctly then it wont and that's a headache for me.

I think you may be referring to the arguments in a command like DoCmd.OpenForm, not different parts of a string.

For example:

DoCmd.OpenForm "CustomerF", , , "CustomerID=" & CustomerID

The commas separate the arguments that OpenForm accepts. The first argument is the form name. The next two arguments are optional, so the extra commas tell Access, "Skip those arguments and use their default values." The last part is the WhereCondition, which tells Access which record to open.

In other words, each comma represents a slot for one of the command's optional parameters. You can't just add or remove commas randomly, but you can leave an optional argument blank if you need to get to one farther down the list.

Access normally helps by showing the parameter list as you type, but you're right: if the beginning isn't valid, IntelliSense often doesn't know what you're trying to do.

If you post one or two of the actual lines you're looking at, I can break down every piece of them for you. I'm not sure I have a specific single video that covers them all. I think I talked about those ones in the OpenForm command, but they're different depending on what you're doing. But if you're having issues with it and have questions about it, I'm sure other people are as well, so this might make for a good video. But I need some more specifics.

Yes like I now know they are called arguments in a command. The open form example I gave I have always fixed either by adding or deleting a comma and it solved my issue. The issue I would have is the form would open to the first record instead of the one specific to the id in the where condition. I just need to learn the structure of the command.

Lee

DoCmd.OpenForm(FormName, View, FilterName, WhereCondition, DataMode, WindowMode, OpenArgs)

DoCmd.OpenForm "CustomerF", , , "CustomerID=" & CustomerID
DoCmd.OpenForm "CustomerF", , , "CustomerID=" & cboCustomer

That’s the stuff I need to learn and understand better. The open form was an example cause it being fairly direct and I have done it so much. If you told me to break it down I would fail the test.

A couple of extra tips.

1) If you have a function with a lot of commas, and you're really only supplying one or two supplemental arguments (such as the Where Condition in the Open Form command) you can use Named Arguments instead of wearing out your comma key. So from Kevin's example above:

DoCmd.OpenForm "CustomerF",,,"CustomerID=" & CustomerID
is the same as
DoCmd.OpenForm "CustomerF", WhereCondition:="CustomerID=" & CustomerID

2) If Intellisense isn't working when it should, such as for the OpenForm command, often times, it may be because either there's already text in a given position or you may have unintentionally pressed a key to clear it.

For example if I type DoCmd.OpenForm "MyFormF", , , and I try to go in between the commas and add something, the Intellisense won't appear unless you go where you want it to appear, make sure there is a space after your cursor then delete the preceding comma and retype it and as long as there is a space Intellisense should appear again.

Kevin and Donald have both given you the key pieces. Named arguments are especially handy once you know what the argument is called, because they make the code much easier to read and you don't have to count commas.

For example:

DoCmd.OpenForm "CustomerF", WhereCondition:="CustomerID=" & CustomerID

Read that as: open CustomerF, where CustomerID equals the CustomerID on the current form. The comma version does exactly the same thing, but it skips the View and FilterName argument slots to get to WhereCondition.

And don't feel bad about not being able to break it down yet. That's just familiarity. After you use a few common commands often enough, you start recognizing their argument lists like you recognize the buttons on your TV remote.

Richard and all thank you for your help. I will get there one day....I Hope.....lol...Donald I have noticed that about Intellisense, and now understand it a bit better....Kevin that is a good break down for me to work with and try to understand better, I tend to understand things better when I am showed examples like you are doing. Thank you to all

You know what they say: "Practice makes better something."

This is true....Have a great weekend!!!!!