You should use really use WM_APP as your base message number instead of WM_USER. Microsoft makes use of WM_USER + n for many internal messages so it can cause operational issues if there is a conflict.
Yes, Registered Windows messages are better. But: 1. You don't have to send these messages between processes. So there are no problems with Microsoft internal messages. 2. Many customers use current constant messages.
Still getting the same error, I am programing in vb6 from a touchscreen running XP and I am using the manufacturer API, do I need to insure that I activate any other references from there list or can I use the hex value from the vb8 example instead of the WM_User. I am rusty with vb6 so all help is appreciated. Thanx
Thanks for that info, I did notice that and made the change that error went away now I am getting and undefined variable for “TFirstForm”, “CKeyboardFirstForm” can you direct me to the solution for this one.