I was wondering why Foxfire! has only one additional source per data item.  I know that it always has (or at least it has since I have been using it), but I have had so many problems because of this.  If there were one or two more sources (making 3 or 4 sources in total) I would have no problems at all.  Is there a trick I can use other than forcing my users to enter other data items to tie the problem data item's sources together?  These items usually have to be summed up so using "SELECT"s in the data item itself is not possible.  I am a SQL database developer if this helps.

Thanks,

Jay

Thanks for the reply.  Here is an example:

Expression:
case when p_taxes.locktax=1 then p_taxes.net_tax else (case when p_jurs_v.value2=0 then p_jurs_v.value1 else p_jurs_v.value2 end)*((case when jurs.factor=0 then ly_jurs.ly_factor*jurs.escalation_factor else jursview.factor end)) * (1-(p_jurs.abate/100)) / (case when p_jurs.install IN (2,6) then 2 else (case when p_jurs.install IN (4,5) then 4 else 1 end) end) end

p_jurs is the root of my relationship tree so it's OK.  My primary source is p_taxes and my additional source is jurs.  This leaves ly_jurs and p_jurs_v without relationship tie-ins.  My user has to enter additional data items (that have ly_jurs and p_jurs_v as either primary sources or secondary sources) and hide them.  The above expression includes 2 views that I have created to remedy some of these problems (I would need about 10 sources to pull from native tables only) caused by having only two sources.  These problems tend to pop-up when I am doing complex estimations.  Love the product, I just thought that allowing users the ability to add an unlimited number of additional sources would be a real plus.

Jay