Results for "Author: james kahl"

Most people know about and use VB's color constants. Most people that I know think green and yellow are a little too bright. Did you know that you can override and change the colors to what you want them to be? Using this technique you can also add your own predfined colors. I have added all of the constants defined in LaVolpe's color picker to show you just some of the possibilities.

I created this for work to maintain a list of databases that we have for different product lines. It uses the Access 10 Object Library to perform this functionality "behind the scenes", so to speak. By doing it this way, you should notice a vast performance increase. NOTE: If you do not have Access 2002, this will not work for you unless you have msacc.olb registered on your system, but there are other options that work in much the same way.

This is the standard windows message box modified with hooks - no additional forms or controls. The way this is compiled, when you reference it in a project it becomes part of the Global Namespace of the project, this means you do not need to make any special declares to start. You just enter it as you would any VB function. It is 100% backward compatible with the VB MsgBox function. You can change all existing MsgBox statements to MsgBoxEx statements with no further coding unless you want to make use of additional parameters. This dll gives the added advantage of setting the font for the message box once and then forgetting about it or you can set the font each time you display a message. Have optimized some of the routines and added ability to perform Translucency.

I created this for work to maintain a list of databases that we have for different product lines. It uses the Access 10 Object Library to perform this functionality "behind the scenes", so to speak. By doing it this way, you should notice a vast performance increase. NOTE: If you do not have Access 2002, this will not work for you unless you have msacc.olb registered on your system, but there are other options that work in much the same way.

Determine if a file exists and retrieve information about size, creation/modifed/access dates and file attributes, this could also be modified to retrieve version information as well. UPDATE: In Response to Solo's statement you can now also retrieve file version info and other information such as company name, file description, default language, etc.

I hate maintaining ImageList controls, especially for larger projects where there might be several forms that can contain two or more of them on each form and have them same images. I prefer instead to use a Resource file for all resources and extract the items as needed. This provides faster load times for forms, creates smaller executables (since you only need one copy of each image), and becomes easier to maintain since all items are located in one place. (Notice there is no .frx file for this project) I loaded all images from the resource file and into the same ImageList control. I also added the capability in this sample to change the size of the toolbar buttons to show another advantage of doing it this way.

I have seen several INI to XML conversion submissions on PSC, but they all seemed to lack some functionality, so I decided to write this. With this class you can convert INI files to compatible XML files and a create a new file. You can also create, delete and edit sections and keys as you wish. I think the editor is pretty easy to use, but have included a Word document that describes how to perform certain tasks. Please let me know what you think, bugs found, or any ideas for improvement.

This is in response to M1K3's submission about centering a form over a picture box. I don't want to rip into the flaws of his methodology and will only say that there were far too many assumptions on his part. I think this method is a much better alternative since you don't need to make sure that your form is a specific size, or the parent form or picture box has their properties set to specific values. Should be good for beginners since I use SystemParametersInfo with SPI_GETNONCLIENTMETRICS to determine border width of forms and height of Titlebars for forms.

Ever get frustrated that when you change the background color of a form the forms border doesn't change as well. Now it can.

This is the standard windows message box modified with hooks - no additional forms or controls. The way this is compiled, when you reference it in a project it becomes part of the Global Namespace of the project, this means you do not need to make any special declares to start. You just enter it as you would any VB function. It is 100% backward compatible with the VB MsgBox function. You can change all existing MsgBox statements to MsgBoxEx statements with no further coding unless you want to make use of additional parameters. This dll gives the added advantage of setting the font for the message box once and then forgetting about it or you can set the font each time you display a message. Have optimized some of the routines and added ability to perform Translucency. Check DevNotes.rtf for latest modifications. Thanks to NCrawler for giving me the information necessary to fix the latest bug I introduced when trying to fix a previous bug.

Most people know about and use VB's color constants. Most people that I know think green and yellow are a little too bright. Did you know that you can override and change the colors to what you want them to be? Using this technique you can also add your own predfined colors. I have added all of the constants defined in LaVolpe's color picker to show you just some of the possibilities.

I created this for work to maintain a list of databases that we have for different product lines. It uses the Access 10 Object Library to perform this functionality "behind the scenes", so to speak. By doing it this way, you should notice a vast performance increase. NOTE: If you do not have Access 2002, this will not work for you unless you have msacc.olb registered on your system, but there are other options that work in much the same way.

Determine if a file exists and retrieve information about size, creation/modifed/access dates and file attributes, this could also be modified to retrieve version information as well. UPDATE: In Response to Solo's statement you can now also retrieve file version info and other information such as company name, file description, default language, etc.

I hate maintaining ImageList controls, especially for larger projects where there might be several forms that can contain two or more of them on each form and have them same images. I prefer instead to use a Resource file for all resources and extract the items as needed. This provides faster load times for forms, creates smaller executables (since you only need one copy of each image), and becomes easier to maintain since all items are located in one place. (Notice there is no .frx file for this project) I loaded all images from the resource file and into the same ImageList control. I also added the capability in this sample to change the size of the toolbar buttons to show another advantage of doing it this way.

I have seen several INI to XML conversion submissions on PSC, but they all seemed to lack some functionality, so I decided to write this. With this class you can convert INI files to compatible XML files and a create a new file. You can also create, delete and edit sections and keys as you wish. I think the editor is pretty easy to use, but have included a Word document that describes how to perform certain tasks. Please let me know what you think, bugs found, or any ideas for improvement.

This is in response to M1K3's submission about centering a form over a picture box. I don't want to rip into the flaws of his methodology and will only say that there were far too many assumptions on his part. I think this method is a much better alternative since you don't need to make sure that your form is a specific size, or the parent form or picture box has their properties set to specific values. Should be good for beginners since I use SystemParametersInfo with SPI_GETNONCLIENTMETRICS to determine border width of forms and height of Titlebars for forms.

Ever get frustrated that when you change the background color of a form the forms border doesn't change as well. Now it can.

This is the standard windows message box modified with hooks - no additional forms or controls. The way this is compiled, when you reference it in a project it becomes part of the Global Namespace of the project, this means you do not need to make any special declares to start. You just enter it as you would any VB function. It is 100% backward compatible with the VB MsgBox function. You can change all existing MsgBox statements to MsgBoxEx statements with no further coding unless you want to make use of additional parameters. This dll gives the added advantage of setting the font for the message box once and then forgetting about it or you can set the font each time you display a message. Have optimized some of the routines and added ability to perform Translucency. Check DevNotes.rtf for latest modifications. Thanks to NCrawler for giving me the information necessary to fix the latest bug I introduced when trying to fix a previous bug.

Most people know about and use VB's color constants. Most people that I know think green and yellow are a little too bright. Did you know that you can override and change the colors to what you want them to be? Using this technique you can also add your own predfined colors. I have added all of the constants defined in LaVolpe's color picker to show you just some of the possibilities.

I created this for work to maintain a list of databases that we have for different product lines. It uses the Access 10 Object Library to perform this functionality "behind the scenes", so to speak. By doing it this way, you should notice a vast performance increase. NOTE: If you do not have Access 2002, this will not work for you unless you have msacc.olb registered on your system, but there are other options that work in much the same way.