That doesn't make sense that you're getting a warning ... you *are* setting the myHistoricalRatesDS in the statement right before the return. I don't get why you have a warning. Now, if you had an if statement in there, it would make sense to me, but the way you're showed it here, it doesn't make sense that there should be a warning.

Of course, I don't use VB, so what do I know?!?!? <g>

~~Bonnie


>I keep getting a lot of "Use of variable prior to assignment" warnings in VB 2005. I know that I can turn them off at the project level and usually do this, but it makes me suspicious that maybe I am doing something that I shouldn't. Here is a snippet in a business class:
>
>

>    Public Function LoadHistoricalRates() As HistoricalRatesDS
>
>        'This is my data access class...
>        Dim myHistoricalRatesData As New HistoricalRatesData
>        'This is my dataset.  I don't instantiate it here because it is instantiated
>        'in my data access class...
>        Dim myHistoricalRatesDS As HistoricalRatesDS
>
>        'An instance of HistoricalRatesDS is instantiated in my data access
>        'class so I don't instantiate it again...
>        myHistoricalRatesDS = myHistoricalRatesData.LoadHistoricalRates
>
>        'Here is where I get the warning...
>        Return myHistoricalRatesDS
>
>    End Function
>