Problem with Mouse Wheel in a sub form

[MaliciousMike]

Hi All,

I posted this in the other post in this forum but it doesn't look like any has read it, and now it's becoming more of an issue to my customers. My appologies for the double post!

I have a form with one subform. I'm using Lebaums mousehook.dll system to stop people from scrolling through records on the main, parent form. This is working fine. The subform doesn't have a record set, it uses VB code to get and send data depending on a number of things. So there is no need for the scroller mouse to be disabled on this form for the purpose of not being able to scroll through records.

HOWEVER.

On the main parent form, there is a memo text box, with scrollbars. Even with the mousehook loaded, users are able to use the mouse wheel to scoll through the text. On the sub form however, uers are UNABLE to use the mousewheel in these text boxes, and there are several text boxes which have a lot of text information in it.

I've tried MouseWheelOFF(False), MouseWheelOFF(True) and both the same again in the subform's OnLoad event, however nothing seems to be working.
Is there a known bug with this?

Any help would be greatly appreciated!


(also, on a side question, what benefit does an application have if you close the recordsets after use? Is it a recommended action, or is it more optional?)

 

[jal]

Can't help you with the mousewheel.

Not only should you close the rs, you must set it to nothing. Believe it or not, I had a loss of data integrity for failing to set it to nothing. (Boy was that one hard to pin down). I ended up with missing columns in my actual table.

But generally, closing a recordset helps to
(1) Make the DB accessible to other users.
(2) Update recordset changes to the DB.
(3) Conserve memory.

 

[Lister]

I don't know if you have seen this, you may have, it should help you with you problem. Good luck, let us know how you get on.