While I can't offer a solution, I can confirm the problem you're having. I'm on 8.2 and I can set any cursor in the VI, but not in the executable. I'm not sure why this is, maybe an applications engineer can shed some light on the problem.
Some of the cursors, such as the paintbrush mentioned in an earlier post, are only relevant in edit mode and you cannot edit a built application. I do not see anything in the documentation, but this may be what is happening. Are the inaccessible cursors ones which are only used in edit mode?
You may be right. Somebody from NI needs to confirm this. However, if that is the case, I should not be able to set the paintbrush cursor in a VI that is running, because it is no longer in edit mode, but in run mode.
Also, I am not able to use custom cursors from a .cur file in a built application even though I successfully use them in a vi.
S G Certified LabVIEW Architect, Certified TestStand Architect, Certified Professional Instructor
This is actually a known issue that some of the cursors will not show up in an executable. R&D is aware of the problem and they are currently working on a solution. One workaround that I am aware of is referencing the cursor in a file. That is Create Cursor From File.vi plus the Set Cursor.vi. However, you will need a cursor file that has the cursor in it. I hope this helps!
Thanks all. I am using a custom cursor file now, and that seems to be a workaround. Be sure to include the cursor file (.cur) in your application if you plan to use this method.
S G Certified LabVIEW Architect, Certified TestStand Architect, Certified Professional Instructor