ListView Question

Try creating a new one to test. Drop the new listview on your form, rename your old listview as lvSearch_Old and call the new one lvSearch. Run the code and test the Item Click.
 
Try creating a new one to test. Drop the new listview on your form, rename your old listview as lvSearch_Old and call the new one lvSearch. Run the code and test the Item Click.

i delete the lvSearch control, rename the module to OLDlvSeacrh_ItemClick, create new control and rename it as lvSearch and same time create a new module of ItemClick. unfortunately nothing happen.
 
Your form has some problems. I experienced errors on the click event and I've just created a new form, copied the controls across, copied the code across and ran it. Everything works fine now.
 
Your form has some problems. I experienced errors on the click event and I've just created a new form, copied the controls across, copied the code across and ran it. Everything works fine now.

i did what you've said, and nothing happened to me, here is the new db.

i guess it has something to do with the access and window version.
 

Attachments

Did you try creating a new listview control in the new form? There's something wrong with the old one it seems.

See the attached, the second listview control.
 

Attachments

Did you try creating a new listview control in the new form? There's something wrong with the old one it seems.

See the attached, the second listview control.

is this working in you access 2013? i opened it and try click an item and nothing happened. therefore if this db is working with your 2013 version then the problem is my access 2013 version.
 
Mine is 2010 and I had to create a new listview control because yours threw errors and it worked fine. Was it the second listview control that you clicked?
 
Mine is 2010 and I had to create a new listview control because yours threw errors and it worked fine. Was it the second listview control that you clicked?

yes, then i guess the problem is my 2013 version.
 
I'm not using the same version of Access as you so we can't conclude that just yet. Test it on another PC with 2013.

... but anyway, if you guys are using 2003 in the office you shouldn't be developing in 2013.
 
I'm not using the same version of Access as you so we can't conclude that just yet. Test it on another PC with 2013.

... but anyway, if you guys are using 2003 in the office you shouldn't be developing in 2013.

ok, the reason why im doing some test in 2013, i was informed that there's an on going upgrade with our os together with ms. anyways i will find another machine with 2013 version and i'll update you about the result. thanks for the effort boss.
 

Users who are viewing this thread

Back
Top Bottom