OCX, Microsoft Common Dialog Control

Matze
Member Posts: 4
Hi,
i tried to use the "Microsoft Common Dialog Control" (comdlg32.ocx) via an ocx variable.
If i try to save my code i get the error message, that there is a designer license missing for the ocx control. Could this be? Do i need a special developer edition of the comdlg32.ocx file?
Has anybody an idea?
Regards
Matthias
i tried to use the "Microsoft Common Dialog Control" (comdlg32.ocx) via an ocx variable.
If i try to save my code i get the error message, that there is a designer license missing for the ocx control. Could this be? Do i need a special developer edition of the comdlg32.ocx file?
Has anybody an idea?
Regards
Matthias
0
Comments
-
Could it be:
Microsoft Knowledge Base Article - 194751
http://support.microsoft.com/default.as ... s%3B194751
Regards,
Bruno0 -
Hello Bruno,
thanks for the information.
But i have no Visual Basic installed. So, if i understand the Knowledge Base Artice in the right way i need to install some development environment from Microsoft (e.g. Visual Basic) to use the ActiveX components from Microsoft. By the way, Navision is (now) also an development environment from Microsoft and i have purchased the C/OCX Granule to use even those Microsoft ActiveX components. This is really incomprehensible to me.
Do do have some other ideas?
Thanks for your assistance.
Best regards,
Matthias0 -
Hi Matthias,
Try this:
regsvr32 c:\winnnt\system32\comdlg32.ocx
(or: regsvr32 c:\windows\system\comdlg32.ocx)
If that doesn't work your comdlg32.ocx is most likely outdated and you need an updated version (which ships with win2000->, I don't know about NT, 98 and 95)
You could aslo use the automation controller instead of the OCX (which only is a wrapper for the dll anyways)
Name DataType Subtype
MSComDialog Automation 'Microsoft Common Dialog Control 6.0 (SP3)'.CommonDialog0 -
Hi Bruno,
i found a solution.
I unregistered the comdlg32.ocx shipped with Win2k and replaced it by an older version (file date 24.06.1998) which shippes with Microsoft Visual Studio 6. At this opportunitiy i copied the file comdlg32.dep to my system and registered the "old" comdlg32.ocx.
Navision now accepts the OCX variable and i can use the Common Dialog Control. This i a really unorthodox solution, but i works ;-)
Anyway, i talk to my NSC to open a support call with Microsoft to check this problem.
I like to thank you. You took me on the right way.
Best regards,
Matthias
P.S.: This solution works also on my second developer machine!?0 -
hello. does this got fixed yet? i still get the same problem with ms comdlg sp3.0
-
In you codeunit change the ID of the function where you are using the MS Comdlg to 400, and you should be able to compile and use it.0
Categories
- All Categories
- 73 General
- 73 Announcements
- 66.6K Microsoft Dynamics NAV
- 18.7K NAV Three Tier
- 38.4K NAV/Navision Classic Client
- 3.6K Navision Attain
- 2.4K Navision Financials
- 116 Navision DOS
- 851 Navision e-Commerce
- 1K NAV Tips & Tricks
- 772 NAV Dutch speaking only
- 617 NAV Courses, Exams & Certification
- 2K Microsoft Dynamics-Other
- 1.5K Dynamics AX
- 320 Dynamics CRM
- 111 Dynamics GP
- 10 Dynamics SL
- 1.5K Other
- 990 SQL General
- 383 SQL Performance
- 34 SQL Tips & Tricks
- 35 Design Patterns (General & Best Practices)
- 1 Architectural Patterns
- 10 Design Patterns
- 5 Implementation Patterns
- 53 3rd Party Products, Services & Events
- 1.6K General
- 1.1K General Chat
- 1.6K Website
- 83 Testing
- 1.2K Download section
- 23 How Tos section
- 252 Feedback
- 12 NAV TechDays 2013 Sessions
- 13 NAV TechDays 2012 Sessions