By using this site, you agree to our updated Privacy Policy and our Terms of Use. Manage your Cookies Settings.
434,930 Members | 1,269 Online
Bytes IT Community
+ Ask a Question
Need help? Post your question and get tips & solutions from a community of 434,930 IT Pros & Developers. It's quick & easy.

trying to use the wheelhook A2k version and have a problem

P: n/a
It works fine but when I quit the database. About one in 10 times you
quit and the database closes but I end up with an empty Access sitting
on the screen and the only way to close it is with task manager.

Is this the wheelhook.dll routines?
Is it not unloading and keeping the access program open?

It is the only thing new I have in this database so I assume its it or
something related to it.

Anyone have any ideas on how I should shut down to keep this from
happening?

thanks for any help

Jerry

Jul 25 '06 #1
Share this Question
Share on Google+
4 Replies


P: n/a
sparks wrote:
It works fine but when I quit the database. About one in 10 times you
quit and the database closes but I end up with an empty Access sitting
on the screen and the only way to close it is with task manager.

Is this the wheelhook.dll routines?
Is it not unloading and keeping the access program open?

It is the only thing new I have in this database so I assume its it or
something related to it.

Anyone have any ideas on how I should shut down to keep this from
happening?

thanks for any help

Jerry
I doubt that it's related to the Mousehook dll. That usually happens when
you set an object variable in VBA code and forget to set it to nothing or
from a bug if you implicitly refer to the true/false value of a boolean with
syntax like...

If Me!SomeField Then...

Itstead you need to use either...

If Me!SomeField = True Then...

or

If Me("SomeField") Then...

--
Rick Brandt, Microsoft Access MVP
Email (as appropriate) to...
RBrandt at Hunter dot com
Jul 25 '06 #2

P: n/a
"Rick Brandt" <ri*********@hotmail.comwrote in
news:1N*********************@newssvr13.news.prodig y.com:
That usually happens when
you set an object variable in VBA code and forget to set it to
nothing or from a bug if you implicitly refer to the true/false
value of a boolean with syntax like...

If Me!SomeField Then...

Itstead you need to use either...

If Me!SomeField = True Then...

or

If Me("SomeField") Then...
Or:

If (Me!SomeField) Then

That forces evaluation of the control, and the value is tested, not
the control's Value property.

--
David W. Fenton http://www.dfenton.com/
usenet at dfenton dot com http://www.dfenton.com/DFA/
Jul 25 '06 #3

P: n/a
The only way to prove that the MouseWHeelHook DLL is the problem is to
temporarily comment out your code that calls into my DLL. Open and use then
close your MDB as normal. Repeat 10 times.

If this was a MouseWheelHook issue then I would have heard about it by now.
Quite a few people are using the solution every day.

--

HTH
Stephen Lebans
http://www.lebans.com
Access Code, Tips and Tricks
Please respond only to the newsgroups so everyone can benefit.
"sparks" <js******@swbell.netwrote in message
news:vo********************************@4ax.com...
It works fine but when I quit the database. About one in 10 times you
quit and the database closes but I end up with an empty Access sitting
on the screen and the only way to close it is with task manager.

Is this the wheelhook.dll routines?
Is it not unloading and keeping the access program open?

It is the only thing new I have in this database so I assume its it or
something related to it.

Anyone have any ideas on how I should shut down to keep this from
happening?

thanks for any help

Jerry

Jul 26 '06 #4

P: n/a
On Wed, 26 Jul 2006 03:27:28 GMT, "Stephen Lebans"
<ForEmailGotoMy.WebSite.-WWWdotlebansdot...@linvalid.comwrote:
>The only way to prove that the MouseWHeelHook DLL is the problem is to
temporarily comment out your code that calls into my DLL. Open and use then
close your MDB as normal. Repeat 10 times.

If this was a MouseWheelHook issue then I would have heard about it by now.
Quite a few people are using the solution every day.


Great to hear from everyone.
I went thru and there was one recordset that was not closed in a
function. I fixed that...compacted the database and opened it 10 more
times and could not get it to do it again.
(thanks for the tip)

ps the mousewheel was the last thing that was added to the database
just before the problems.

It all started when I got a call from a person using the database.

We went over to the girls office that is having all the problems just
to see the errors and problems she was having.
I think I found the problem.

First she is using an OLD gateway PIII computer, 256 megs of memory.
They installed winXP pro and office 2003 on it. She is using the
database over the network and just to get it to come up on her system
takes 2-3 minutes.
Then when she closes out it hangs on her every time.

I was surprised that the thing would even run.
So no it is not the mousehook its my missing the recordset and her
trying to run it on this crap.
PS I was told it was a new machine.....
to her it was, it was junk that they dumped on her desk and installed
some new stuff on... she had no idea what it was and to her it was
new.

Jerry
Jul 27 '06 #5

This discussion thread is closed

Replies have been disabled for this discussion.