Results for "Author: mark einhorn"
THE PROBLEM: VB allows regular forms to be instantiated from an ActiveX DLL...but does not allow MDI child forms to be instantiated from an ActiveX DLL! THE SOLUTION: MDIChildMaker! Now you can put your forms in a seperate ActiveX DLL and use them as MDI children forms in your main application's MDI form! NOTE: This is not a trivial example, but uses native VB subclassing techniques. This is one code solution EVERY VB programmer MUST have! Check out www.cyberbiz.com
THE PROBLEM: VB allows regular forms to be instantiated from an ActiveX DLL...but does not allow MDI child forms to be instantiated from an ActiveX DLL! THE SOLUTION: MDIChildMaker! Now you can put your forms in a seperate ActiveX DLL and use them as MDI children forms in your main application's MDI form! NOTE: This is not a trivial example, but uses native VB subclassing techniques. This is one code solution EVERY VB programmer MUST have! Check out www.cyberbiz.com
THE PROBLEM: VB allows regular forms to be instantiated from an ActiveX DLL...but does not allow MDI child forms to be instantiated from an ActiveX DLL! THE SOLUTION: MDIChildMaker! Now you can put your forms in a seperate ActiveX DLL and use them as MDI children forms in your main application's MDI form! NOTE: This is not a trivial example, but uses native VB subclassing techniques. This is one code solution EVERY VB programmer MUST have! Check out www.cyberbiz.com
THE PROBLEM: VB allows regular forms to be instantiated from an ActiveX DLL...but does not allow MDI child forms to be instantiated from an ActiveX DLL! THE SOLUTION: MDIChildMaker! Now you can put your forms in a seperate ActiveX DLL and use them as MDI children forms in your main application's MDI form! NOTE: This is not a trivial example, but uses native VB subclassing techniques. This is one code solution EVERY VB programmer MUST have! Check out www.cyberbiz.com
THE PROBLEM: VB allows regular forms to be instantiated from an ActiveX DLL...but does not allow MDI child forms to be instantiated from an ActiveX DLL! THE SOLUTION: MDIChildMaker! Now you can put your forms in a seperate ActiveX DLL and use them as MDI children forms in your main application's MDI form! NOTE: This is not a trivial example, but uses native VB subclassing techniques. This is one code solution EVERY VB programmer MUST have! Check out www.cyberbiz.com
THE PROBLEM: VB allows regular forms to be instantiated from an ActiveX DLL...but does not allow MDI child forms to be instantiated from an ActiveX DLL! THE SOLUTION: MDIChildMaker! Now you can put your forms in a seperate ActiveX DLL and use them as MDI children forms in your main application's MDI form! NOTE: This is not a trivial example, but uses native VB subclassing techniques. This is one code solution EVERY VB programmer MUST have! Check out www.cyberbiz.com
THE PROBLEM: VB allows regular forms to be instantiated from an ActiveX DLL...but does not allow MDI child forms to be instantiated from an ActiveX DLL! THE SOLUTION: MDIChildMaker! Now you can put your forms in a seperate ActiveX DLL and use them as MDI children forms in your main application's MDI form! NOTE: This is not a trivial example, but uses native VB subclassing techniques. This is one code solution EVERY VB programmer MUST have! Check out www.cyberbiz.com
THE PROBLEM: VB allows regular forms to be instantiated from an ActiveX DLL...but does not allow MDI child forms to be instantiated from an ActiveX DLL! THE SOLUTION: MDIChildMaker! Now you can put your forms in a seperate ActiveX DLL and use them as MDI children forms in your main application's MDI form! NOTE: This is not a trivial example, but uses native VB subclassing techniques. This is one code solution EVERY VB programmer MUST have! Check out www.cyberbiz.com
THE PROBLEM: VB allows regular forms to be instantiated from an ActiveX DLL...but does not allow MDI child forms to be instantiated from an ActiveX DLL! THE SOLUTION: MDIChildMaker! Now you can put your forms in a seperate ActiveX DLL and use them as MDI children forms in your main application's MDI form! NOTE: This is not a trivial example, but uses native VB subclassing techniques. This is one code solution EVERY VB programmer MUST have! Check out www.cyberbiz.com
THE PROBLEM: VB allows regular forms to be instantiated from an ActiveX DLL...but does not allow MDI child forms to be instantiated from an ActiveX DLL! THE SOLUTION: MDIChildMaker! Now you can put your forms in a seperate ActiveX DLL and use them as MDI children forms in your main application's MDI form! NOTE: This is not a trivial example, but uses native VB subclassing techniques. This is one code solution EVERY VB programmer MUST have! Check out www.cyberbiz.com
THE PROBLEM: VB allows regular forms to be instantiated from an ActiveX DLL...but does not allow MDI child forms to be instantiated from an ActiveX DLL! THE SOLUTION: MDIChildMaker! Now you can put your forms in a seperate ActiveX DLL and use them as MDI children forms in your main application's MDI form! NOTE: This is not a trivial example, but uses native VB subclassing techniques. This is one code solution EVERY VB programmer MUST have! Check out www.cyberbiz.com
THE PROBLEM: VB allows regular forms to be instantiated from an ActiveX DLL...but does not allow MDI child forms to be instantiated from an ActiveX DLL! THE SOLUTION: MDIChildMaker! Now you can put your forms in a seperate ActiveX DLL and use them as MDI children forms in your main application's MDI form! NOTE: This is not a trivial example, but uses native VB subclassing techniques. This is one code solution EVERY VB programmer MUST have! Check out www.cyberbiz.com
THE PROBLEM: VB allows regular forms to be instantiated from an ActiveX DLL...but does not allow MDI child forms to be instantiated from an ActiveX DLL! THE SOLUTION: MDIChildMaker! Now you can put your forms in a seperate ActiveX DLL and use them as MDI children forms in your main application's MDI form! NOTE: This is not a trivial example, but uses native VB subclassing techniques. This is one code solution EVERY VB programmer MUST have! Check out www.cyberbiz.com
THE PROBLEM: VB allows regular forms to be instantiated from an ActiveX DLL...but does not allow MDI child forms to be instantiated from an ActiveX DLL! THE SOLUTION: MDIChildMaker! Now you can put your forms in a seperate ActiveX DLL and use them as MDI children forms in your main application's MDI form! NOTE: This is not a trivial example, but uses native VB subclassing techniques. This is one code solution EVERY VB programmer MUST have! Check out www.cyberbiz.com