I. Method 1:
Click the pb Environment system tree window, right-click the first tab, and find the control you want and drag it to your window, as shown in:
Ii. Fang 2:
1. symptom: When an OLE control is inserted in powerbuilder and an insert control is clicked, the application is automatically closed,
During online queries, some people say that it is caused by conflicts between ocx (such as Jinshan and superstar). After all, there are a lot of software today. How can we know that this is caused by software conflicts?
2. Principle Analysis
When you click insert control in the OLE control, pb searches for the available controls and displays them in PB.
The position of the PB search control is the subitem (DLL and OCX file registration information) under "HKEY_CLASSES_ROOT/CLSID" in the registry)
The saved location is: "HKEY_CURRENT_USER/Software/Sybase/PowerBuilder/8.0/OLE Object Bitmaps /..."
That is to say, the sub-item of pb search CLSID is saved in OLE Object Bitmaps. When the DLL or OCX control in the search CLSID conflicts with PB, the DLL and OCX controls after CLSID are not stored in OLE Object Bitmaps. That is to say, OLE Object Bitmaps does not fully load all controls. Some control conflicts cause interruptions and lead to PB errors, identifying conflicting controls is critical.
3. Practice
(1) run the Registry
(2) Find "HKEY_CLASSES_ROOT/CLSID" in the registry, export and save it as CLSID. REG, and open it in notepad.
(3) in the registry, find "HKEY_CURRENT_USER/Software/Sybase/PowerBuilder/8.0/OLE Object Bitmaps /... "The Last subitem in, for example," 0E59F1D5-1FBE-11D0-8FF2-00A0D10038BC ", proves that the control before this subitem is correct.
(4) Open CLSID in notepad. REG, and search for the last subitem of OLE Object Bitmaps, for example, "0E59F1D5-1FBE-11D0-8FF2-00A0D10038BC". keep searching until the prompt is not found. By now, all the controls above notepad are correct. Then, use the keyword "ToolboxBitmap32" and search for it. Find the first keyword with "ToolboxBitmap32" and "control,
The control that proves the problem is "C:/windows/system32/aliedit. dll", and then enter
If you are prompted that the reverse registration is successful, open the pb ole control to check whether an error is reported. If an error is returned, return to step (3) for loop search. If you cannot find the path, delete the entire subitem in "HKEY_CLASSES_ROOT/CLSID. Generally, only one or two widgets conflict, so you don't have to worry about heavy workload.
(5) Success