Windows Develop Bookmark and Share   
 index > Windows Forms Designer > Unable to get the window handle for the 'AxRHTemp' control. Windowless ActiveX controls are not supported.
 

Unable to get the window handle for the 'AxRHTemp' control. Windowless ActiveX controls are not supported.

Hi Everyone,

I am having a problem to run my application as it gives me the following error:

Unable to get the window handle for the 'AxRHTemp' control. Windowless ActiveX controls are not supported.

Windows and VS2008 versions:

1. Windows XP professional version 5.1(build 2600.xpsp_sp3_gdr.080814-1236:Service pack3)

2. Visual Studio version 9.0.30729.1 SP -.Net Framework version 3.5 SP1

3. PC -Dell Optiplex 755 duo core2

Could someone provide some tips as how to correct this issue?

Thanks,

Frank

Frank2K  Tuesday, January 27, 2009 7:16 PM

Hi Frank2K,

Any .Net application won't have direct relative with hardware. It related with the .Net Framework. Since I am not familiar with that component. If it call some native API that will related to the driver installed on your computer, then it will have some relative with your hardware. But base on the error message, I think it should be some problem with the .Net Framework instead of the driver. May be you can try to reinstall the framework to see if the problem can be fixed.

Sincerely,
Kira Qian


Please mark the replies as answers if they help and unmark if they don't.
Kira Qian  Wednesday, February 04, 2009 1:39 AM

Hi Frank2K,

What does "AxRHTemp" control? I never heard about it.

What kind of application did you develop? Why did you use that component?

Sincerely,
Kira Qian


Please mark the replies as answers if they help and unmark if they don't.
Kira Qian  Thursday, January 29, 2009 6:38 AM

Hi Kira,

What does "AxRHTemp" control? I never heard about it.

This is an activeX control that is used with the NEWPORT® iTCX transmitter that monitors Temperature from two independent Thermocouple channels over an Ethernet network or the Internet.

What kind of application did you develop? Why did you use that component?

I developed a VB.Net (VS2008) to measure temperature and I am using this activeX control as is the only way that I could talk to this device:

Here is the link to this device:

http://www.newportus.com/i/iTCX.htm

AxInterop.RHTemp_ActiveX.dll
Interop.RHTemp_ActiveX.dll
RHTemp.ocx


Thanks very much,

Frank

Frank2K  Friday, January 30, 2009 5:11 PM

Hi Frank2K,

I am sorry we cannot serve that component. It's a third part component, we haven't tested it. You may try to contact the company who sales it for the necessary information of "the correct way to use it in a .Net based application".

Thank you for your understanding.

Sincerely,
Kira Qian


Please mark the replies as answers if they help and unmark if they don't.
Kira Qian  Monday, February 02, 2009 2:18 AM
Hi Kira,

Thanks for your reply and just wonder what this error means and possible reasons that this application was working fine on a previous dell PC but not on Dell's Optiplex 755 duo core2.

Thanks again,

Frank

Frank2K  Monday, February 02, 2009 6:28 PM

Hi Frank2K,

Base on my knowledge of VC++, each control such as EditControl, ComboBox is recognized as a Window, It is managed by a point or called window handle, When we create a control, we need to create a window handle in order to manage that control. The error message indicated it met some problem when creating the Window handle.

Sincerely,
Kira Qian


Please mark the replies as answers if they help and unmark if they don't.
Kira Qian  Tuesday, February 03, 2009 2:40 AM
Thanks again Kira,

However, any ideas why worked fine with a Dell's Optiplex 745 duo core2, but not with Dell's Optiplex 755 duo core2? Could some files were missing?

Frank

Frank2K  Tuesday, February 03, 2009 6:38 PM

Hi Frank2K,

Any .Net application won't have direct relative with hardware. It related with the .Net Framework. Since I am not familiar with that component. If it call some native API that will related to the driver installed on your computer, then it will have some relative with your hardware. But base on the error message, I think it should be some problem with the .Net Framework instead of the driver. May be you can try to reinstall the framework to see if the problem can be fixed.

Sincerely,
Kira Qian


Please mark the replies as answers if they help and unmark if they don't.
Kira Qian  Wednesday, February 04, 2009 1:39 AM
Thanks,

Frank

Frank2K  Friday, February 06, 2009 6:24 PM
Hi frank, i'm having the same problem, but i'm sure it's not a dell issue. i believe it's a windows vista related problem. you probably change the OS when you got the new dell, right?

i don't have the solution for this issue yet
joaopsr  Monday, July 13, 2009 10:27 AM

You can use google to search for other answers

Custom Search

More Threads

• There is already a command handler for the menu command '5efc7975-14bc-11cf-9b2b-00aa00573819 : 17'
• Cannot drag (move) controls in designer - control is deleted on drag operation.
• Dragging ActiveX Control in the Designer Area which needs a License Key
• Query Builder
• listview over picturebox
• Monotype fonts for list boxes
• listBox or listView: 1 item=Multiple rows with formatting
• Showing context menus with the DesignSurface class.
• Error message when switchign between designer and code view
• System.ComponentModel.Design.ExceptionCollection thrown in user control subclass