Results for "Author: richard petithory"
compile this Dll into a folder in you VB folder with any name. try it out on some code.
This code is a VB6 Add-on that, when compiled as a Dll into your VB directory will place itself in the Add-ons menu. When run, it will open up a window showing you all the variables you have declared but have not used anywhere. why would you want to know this? I work for a company writing a VB app that is 600,000 lines long right now. you can save yourself about 8 megs of memory consumption this way.
Uses a few API calls to enumerate a list of users on a remote windows system.
compile this Dll into a folder in you VB folder with any name. try it out on some code.
This code is a VB6 Add-on that, when compiled as a Dll into your VB directory will place itself in the Add-ons menu. When run, it will open up a window showing you all the variables you have declared but have not used anywhere. why would you want to know this? I work for a company writing a VB app that is 600,000 lines long right now. you can save yourself about 8 megs of memory consumption this way.
Uses a few API calls to enumerate a list of users on a remote windows system.
compile this Dll into a folder in you VB folder with any name. try it out on some code.
This code is a VB6 Add-on that, when compiled as a Dll into your VB directory will place itself in the Add-ons menu. When run, it will open up a window showing you all the variables you have declared but have not used anywhere. why would you want to know this? I work for a company writing a VB app that is 600,000 lines long right now. you can save yourself about 8 megs of memory consumption this way.
Uses a few API calls to enumerate a list of users on a remote windows system.
compile this Dll into a folder in you VB folder with any name. try it out on some code.
This code is a VB6 Add-on that, when compiled as a Dll into your VB directory will place itself in the Add-ons menu. When run, it will open up a window showing you all the variables you have declared but have not used anywhere. why would you want to know this? I work for a company writing a VB app that is 600,000 lines long right now. you can save yourself about 8 megs of memory consumption this way.
Uses a few API calls to enumerate a list of users on a remote windows system.
Place this control on a form along with two other controls (text boxes, etc). In the forms Load method, place the following code (this example is for two text boxes... if you can't figure this out, un-install VB from your computer) WESplitter1.LeftChild Text1.hwnd, Text1 WESplitter1.RightChild Text2.hwnd, Text2
compile this Dll into a folder in you VB folder with any name. try it out on some code.
This code is a VB6 Add-on that, when compiled as a Dll into your VB directory will place itself in the Add-ons menu. When run, it will open up a window showing you all the variables you have declared but have not used anywhere. why would you want to know this? I work for a company writing a VB app that is 600,000 lines long right now. you can save yourself about 8 megs of memory consumption this way.
Uses a few API calls to enumerate a list of users on a remote windows system.
Place this control on a form along with two other controls (text boxes, etc). In the forms Load method, place the following code (this example is for two text boxes... if you can't figure this out, un-install VB from your computer) WESplitter1.LeftChild Text1.hwnd, Text1 WESplitter1.RightChild Text2.hwnd, Text2
compile this Dll into a folder in you VB folder with any name. try it out on some code.
This code is a VB6 Add-on that, when compiled as a Dll into your VB directory will place itself in the Add-ons menu. When run, it will open up a window showing you all the variables you have declared but have not used anywhere. why would you want to know this? I work for a company writing a VB app that is 600,000 lines long right now. you can save yourself about 8 megs of memory consumption this way.
Uses a few API calls to enumerate a list of users on a remote windows system.