asked on
Requerying a listbox
I have a Listobx on a form (Form_A) that is populated by Table_A
There is a button on the same Form_A to Add a record to Table_A.
-CLicking on the "Add" button opens a new form (Form_B) to enter information. Once this information is entered, the information is Inserted into Table_A, and Form_B closes.
The Problem now is that there is new data in Table_A, and the listbox on Form_A has not updated to reflect this.
In my VBA code for the "Add" button on Form A I have tried the following to requery the listbox (thinking it would do the requery after returning from Form_B)
DoCmd.OpenForm stDocName, , , stLinkCriteria, , , CStr(Me.lstTrips.value)
Me.lstAffected.Requery
This did not work, as the Me.lstAffected.Requery would happen before new data was entered on From_B
So now, directly inside the Form_B VBA code, after I execute my SQL statement to add the data, I tried:
Forms.frmModuleData_Trip.l
But then I get an error "Object does not support that property or method."
How can I get my listBox on Form_A to requery from VBA code in Form_B?
thanks
There is a button on the same Form_A to Add a record to Table_A.
-CLicking on the "Add" button opens a new form (Form_B) to enter information. Once this information is entered, the information is Inserted into Table_A, and Form_B closes.
The Problem now is that there is new data in Table_A, and the listbox on Form_A has not updated to reflect this.
In my VBA code for the "Add" button on Form A I have tried the following to requery the listbox (thinking it would do the requery after returning from Form_B)
DoCmd.OpenForm stDocName, , , stLinkCriteria, , , CStr(Me.lstTrips.value)
Me.lstAffected.Requery
This did not work, as the Me.lstAffected.Requery would happen before new data was entered on From_B
So now, directly inside the Form_B VBA code, after I execute my SQL statement to add the data, I tried:
Forms.frmModuleData_Trip.l
But then I get an error "Object does not support that property or method."
How can I get my listBox on Form_A to requery from VBA code in Form_B?
thanks
Microsoft Access
Last Comment
jondecker76
'Forms.frmModuleData_Trip.
I would have expected the code to work.
It might worth trying with different syntax..
Forms("frmModuleData_Trip"
I would have expected the code to work.
It might worth trying with different syntax..
Forms("frmModuleData_Trip"
ASKER
Tried the different syntax. I get an error that "Project can't find the form 'frmModuleData_Trip' referred to in a Macro Expression or VBA code."
But I assure you that frmModuleData_Trip does indeed exist in the project. At the time that Form_B is called, frmModuleData_Trip is a subform nested 2 layers deep, if that makes a difference.
I can take screenshots if you want, but again, frmModuleData_Trip does exist!
But I assure you that frmModuleData_Trip does indeed exist in the project. At the time that Form_B is called, frmModuleData_Trip is a subform nested 2 layers deep, if that makes a difference.
I can take screenshots if you want, but again, frmModuleData_Trip does exist!
Not as far as Access is concerned it doesn't!
Once it's a subform it's just a control in another form.
Yes it makes an enormous difference!
To get 2 levels down you need a lengthy reference
Forms!mainformname!sub1nam
Once it's a subform it's just a control in another form.
Yes it makes an enormous difference!
To get 2 levels down you need a lengthy reference
Forms!mainformname!sub1nam
ASKER
Ok I will test this out..
But, why is this so ugly? I have programed in C, C++, Ruby, PHP, Python and a few other lesser-known languages, and have never seen such horrible structure. Is it something that I am doing wrong while learning VBA, or is it just in the nature of VBA?
For example, what I am trying to accomplish is simple:
Click a button to add a new entry to a listbox
this opens a new form to fill in new data
click a button on that new form to insert that data in the database and close this form
Update a listbox to show the changes
It would be considered good programming practice to do this all in one place (for maintainability), but VBA is forcing me to have some code in the OnCLick() event, then other code in the new form to update the list.
If I change how it works in the future, I would have to remember that the list gets refreshed from another form..
DOes anyone see my point? Can anyone offer any suggestions in learning to deal with this in VBA?
But, why is this so ugly? I have programed in C, C++, Ruby, PHP, Python and a few other lesser-known languages, and have never seen such horrible structure. Is it something that I am doing wrong while learning VBA, or is it just in the nature of VBA?
For example, what I am trying to accomplish is simple:
Click a button to add a new entry to a listbox
this opens a new form to fill in new data
click a button on that new form to insert that data in the database and close this form
Update a listbox to show the changes
It would be considered good programming practice to do this all in one place (for maintainability), but VBA is forcing me to have some code in the OnCLick() event, then other code in the new form to update the list.
If I change how it works in the future, I would have to remember that the list gets refreshed from another form..
DOes anyone see my point? Can anyone offer any suggestions in learning to deal with this in VBA?
"It would be considered good programming practice to do this all in one place "
Really? Wouldn't you want the object and the code to move together if you re-used the object?
Really? Wouldn't you want the object and the code to move together if you re-used the object?
ASKER
Yes, that is what I said - all in one place...
Ideally, my Form_B (in my example) could work to populate the database, and could be opened by any form. But now, since I had to break up my code, and there is a hard-coded requery pointing back to a specific form, now it can't be re-used.
VBA forces you to break what I would consider good programming practice, and now I have code in 2 places, making maintainability bad, as well as not being able to re-use things because of the now hard-coded requery.
Is it something that I'm doing wrong and not understanding, or is it just how things are with VBA?
Ideally, my Form_B (in my example) could work to populate the database, and could be opened by any form. But now, since I had to break up my code, and there is a hard-coded requery pointing back to a specific form, now it can't be re-used.
VBA forces you to break what I would consider good programming practice, and now I have code in 2 places, making maintainability bad, as well as not being able to re-use things because of the now hard-coded requery.
Is it something that I'm doing wrong and not understanding, or is it just how things are with VBA?
ASKER CERTIFIED SOLUTION
THIS SOLUTION ONLY AVAILABLE TO MEMBERS.
View this solution by signing up for a free trial.
Members can start a 7-Day free trial and enjoy unlimited access to the platform.
ASKER
Wow, I never knew that - this is exactly what I was looking for!
try this
Forms![frmModuleData_Trip]
is frmModuleData_Trip the name of Form A you mentioned above?