Turn on suggestions
Auto-suggest helps you quickly narrow down your search results by suggesting possible matches as you type.
Showing results for
Topic Options
- Subscribe to RSS Feed
- Mark Topic as New
- Mark Topic as Read
- Float this Topic for Current User
- Bookmark
- Subscribe
- Mute
- Printer Friendly Page
I have a Visual Basic application that is also an ActiveX server. L
yaakov
Member
08-12-2001 09:54 AM
Options
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report to a Moderator
abWindows 5.5 recognizes the controls and I can use them (methods and properties). LabVIEW 6i doesn't recognize it at all. When this same application was released to be only an ActiveX control, LabWindows and LabVIEW could both work with it. What happened?
codeman
Member
08-13-2001 12:00 PM
Options
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report to a Moderator
abWindows 5.5 recognizes the controls and I can use them (methods and properties). LabVIEW 6i doesn't recognize it at all. When this same application was released to be only an ActiveX control, LabWindows and LabVIEW could both work with it. What happened?What do you mean by doesn't work with LabVIEW 6? Are you able to create an automation refnum for it? Is it in the list of registered servers? Do the methods and properties show up in the nodes? Do you get any error messages from the Automation Open or from the nodes? You might want to make sure you have the 6.0.2 patch before you do too much digging into this.
08-14-2001 01:21 AM
Options
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report to a Moderator
abWindows 5.5 recognizes the controls and I can use them (methods and properties). LabVIEW 6i doesn't recognize it at all. When this same application was released to be only an ActiveX control, LabWindows and LabVIEW could both work with it. What happened?It wasn't a LabVIEW problem after all. I had intsalled a final release on top of a beta-release of my ActiveX server and Windows got its knickers in a twist. After cleaning up the registry. LabVIEW used the ActiveX server like a charm. Thanks for extended help anyway.
08-14-2001 01:21 AM
Options
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report to a Moderator
abWindows 5.5 recognizes the controls and I can use them (methods and properties). LabVIEW 6i doesn't recognize it at all. When this same application was released to be only an ActiveX control, LabWindows and LabVIEW could both work with it. What happened?It wasn't a LabVIEW problem after all. I had intsalled a final release on top of a beta-release of my ActiveX server and Windows got its knickers in a twist. After cleaning up the registry. LabVIEW used the ActiveX server like a charm. Thanks for extended help anyway.
