Thanks Sean for the quick reply. I actually already use the list method to store values. My problem is that over the course of the next year or two, I will be greatly expanding my program. With this current method, I will have to redefine my lists with every addition or subtraction of nuclides.
Additionally, my code is set up to run and compare evaluations utilizing different constants:
\[CapitalGamma]Co60[]=100 (*Constant from ENDF library*)
\[CapitalGamma]Co60[]=98.8 (*Constant from JEFF 3.1 library*)
\[Lambda]Co60[]=0.53 (*Constant from ENDF library*)
\[Lambda]Co60[]=0.44 (*Constant from JEFF 3.1 library*)
And I am afraid that if I can't do this dynamically, my code may get a little messy utilizing lists with my array based method:
Except the length of each row of Co60Constants is going to be incredibly long and dependent on the other variables introduced into the system. With the "standard" way of creating and declaring variables, I will be editing hundreds of matrices with each addition of nuclides into my system. And if I change variables (i.e. instead of Co60 I use Sr90), I will have to redefine everything. Plus, it's going to be very difficult to keep track of which position in the list represents what constant. I'm not sure if what I've written here makes my problem more clear, I can expand on it if I need to.
Maybe the short answer (and the one you've already given) is that I can't generate variables. I guess I don't really want to accept how inefficient the process is going to be, but maybe that is the only way to do it.