Nevermind... I worked it out on my own.
For those of you pondering the reason why it did that in the first
place...you guessed it... bug in VB (no thanx to MS).
The workaround:
Set up the pointer (.cur file) as a RESOURCE, then do a
objectname.MouseIcon = LoadResPicture(ResID, vbResCursor)
in your Form_Load event to assign it to the objects you want.
Running it from the IDE, will STILL display the pointer in
monochrome, but once your program is compiled and installed,
it'll start showing up in color... ya just gotta trust it.
"CajunCoiler (http://www.cajuncoiler.tk)"
<po**********@totallyspamless.cox.net> wrote in message
news:scylb.99912$a16.59283@lakeread01...
Here's one that's been gnawing at me all day... Why is it when I
attempt to use a 16-color custom pointer (MousePointer = 99,
MouseIcon="thefinger.cur") that at run-time, all the colors wash
out, and a monochrome cursor is displayed?
This behavior takes place regardless of the type of object that
its pointing to... What gives?