I am creating a module that works with (monthly) mutual fund returns.
I would appreciate it if you could help me out with the right structure of my Data Access Layer (DAL). The current structure seems unnecessarily complex.

In SQL Server I have a table to store the monthly returns of a lot of mutual funds.
The table has the following fields:
id
MutualFundName
Month
Return

I created a MutualFundReturnInfo class in my DNN module with the same properties. 1 instance of the MutualFundReturnInfo class contains 1 monthly return for 1 mutual fund. But I need to work with all the monthly returns (of 1 mutual fund), not just the return for 1 month (of 1 mutual fund). Therefore I created a List(Of MutualFundReturnsInfo).
But I'm doing calculations on the returns with an external statistical program that only works with arrays (not with my List(Of MutualFundReturnsInfo)).
So I have to extract the monthly returns out of this List(Of MutualFundReturnsInfo) (into an array).
Because the List(Of MutualFundReturnsInfo) also contains the id, MutualFundName and Month. (I do need this information later on.)

Is this the best approach or is there a better and easier way to work with the monthly returns? My current structure seems unnecessarily complex.

Help is much appreciated.

Hi ,

If you are  doing external calc. on data than i don't think so your approch is good but what i suggest is do your return calculation in backend in your SP if possible and return SQL result directly to frontend side. So you can directly bind into contol.

So in future if any change than you can directly change calc. logic in SP.

 thanks

Sahilmahammad

oh, i thought you are using DB server like SQL or Oracle so that's why i am suggsting SP (Store Procedure).

Any ways, one thing i can suggest is , once you are calculating return you can cache it and used this 'll help you to improve application perfomance. As your using DNN you don't have to worry about caching because it's giving class ready to use.

May this help.

Sahilmahamammad