I have multiple (8-10) subroutines that I call over and over in my application to fill combo boxes.
Right now, the routines are in each form's .vb code file.
I want to have one set of routines that I can call from anywhere in the application.
I have tried creating a 'library' by putting all the subroutines in one .vb file and making them all public shared. I added (byref sender) to each one and converted all the references in each one from me to sender.

It didn't work. The combo boxes didn't get populated.

Any clues to get me on the correct path?

Thanks,
Karen

Couple of things. Does the class (.vb) file exist in the same namespace as your project? Without going into a lengthy detail if you created the class file inside of a folder it will not belong to the default namespace it will belong to: (This is the behavior in C# and I haven't worked in VB in a long time, but I am assuming the behavior is the same)

[namespace].[foldername]

and you will need to add an import statement to access your class (or use the fully qualified name: namespace.foldername.[classname] )

Also, is the CLASS declared as public or protected?

hth.

================================================== =========
Read this if you want to know how to get a correct reply for your question:
http://www.catb.org/~esr/faqs/smart-questions.html
================================================== =========
Technical Editor for: Professional Search Engine Optimization with ASP.NET
http://www.wiley.com/WileyCDA/WileyT...470131470.html
================================================== =========
Why can't Programmers, program??
http://www.codinghorror.com/blog/archives/000781.html
================================================== =========

As with everything in this forum there are always multiple options available. Here is mine:

1.) Create a module for your application.
2.) Create a public function that passes a combo box
    from your form as a parameter and returns a combo box
    as a value.

Example:

Module Module1

    Public Function fncFillComboBox(ByVal cbo As ComboBox) As ComboBox

        '* Simply filling the combobox with numbers.
        For intX As Integer = 0 To 5
            cbo.Items.Add(intX.ToString)
        Next

        cbo.SelectedIndex = 0

        '* Return the combobox to your calling form.
        fncFillComboBox = cbo

    End Function

End Module

Assuming a simple example form with a button and a combo box
here is sample code to fill your combo box:

Public Class Form1

    Private Sub Button1_Click(ByVal sender As System.Object, ByVal e As System.EventArgs) Handles Button1.Click
        Me.ComboBox1 = Module1.fncFillComboBox(Me.ComboBox1)
    End Sub

End Class

You could easily change the example function to pass not only the combo box but also an SQL statement that could be processed within the function.




Best Regards,
Earl Francis

Nicely done Earl ^^

================================================== =========
Read this if you want to know how to get a correct reply for your question:
http://www.catb.org/~esr/faqs/smart-questions.html
================================================== =========
Technical Editor for: Professional Search Engine Optimization with ASP.NET
http://www.wiley.com/WileyCDA/WileyT...470131470.html
================================================== =========
Why can't Programmers, program??
http://www.codinghorror.com/blog/archives/000781.html
================================================== =========

No, this behavior is not consistent between C# and VB.

A new class created in a folder in C# using Visual Studio will result in the class being contained in the project's root namespace plus the folder name as Doug offered. However, you can MOVE a class file into a folder and the class will not take on the folder name as another "branch" in its namespace. This behavior is strictly a VS.NET "feature" when you add a class file.

In VB.NET, be default class files (regular classes as well as web forms and similar entities) do not include a namespace declaration. Therefore, they simply take the project default namespace as their namespace.

A combobox is an object. Even when passing it "ByVal" in VB, you are still just passing the value of the object reference so you don't need to return anything from this type of method.

When you DO need to return a value, it's cleaner to use the "Return" keyword instead of the old vb style:

    <function name>=<return value>

just use:

    Return <return value>

-Peter

Peter,
  Point taken. It does clean up the code.



Best Regards,
Earl Francis