abjMouseWheel

  • Thread starter Thread starter David
  • Start date Start date
This is interesting because I am experiencing the same phenomena on 2
different computers. Sounds to me like a setting problem that I have in
common with these two machines.
 
I am using Vista x64 on one and Vista x32 on the other. Both of them have
all the updates for Office, Windows, etc.
 
I doubt it is the mouse settings. If you notice in the code I sent you,
there is some other code dealing with converting decimal places and that
isn't working either.
I thought at first that maybe it had something to do with Location but why
would it work when I newly import and then not after I close and re-open it?
Are there any other settings in Access that could affect location just being
able to spot the module in order to function?
David
 
I tested it on Windows XP. Not really sure if that has anything to with it
but it might??? Didf you get the one I returned? Is it still doing the
same thing? I fixed the References and was hoping that made a difference on
your end.

--
Gina Whipp

"I feel I have been denied critical, need to know, information!" - Tremors
II

http://www.regina-whipp.com/index_files/TipList.htm
 
David,

Oops, I forgot the *MakeCurrency* isn't being called so no way for it to
work. You have it in the module but you aren't actually Calling it.

Call MakeCurrency(NameOfControl)

I thought you said you had it in a Trusted Location?


--
Gina Whipp

"I feel I have been denied critical, need to know, information!" - Tremors
II

http://www.regina-whipp.com/index_files/TipList.htm
 
Well, by your suggestion, I once again checked the Trusted Location.
Although, the "wizard was in a trusted location, the actual database was
NOT. This fixed it.
Thank you very much for your help!
Daved
 
As a last resort, you could try unistalling and reinstalling the access
suite...

--
Jack Leach
www.tristatemachine.com

"I haven''t failed, I''ve found ten thousand ways that don''t work."
-Thomas Edison (1847-1931)
 
Back
Top