On 25/07/06, [EMAIL PROTECTED] wrote: > No need to get tetchy, I was only asking...
I wasn't getting tetchy - I was only telling :-) > No offence intended, but my experience with academia has not always been > equitable. A good number of academic types have responded with "won't" > rather than "can't". Ah,but I'm not an academic - I'm a techie. I just have to *work* with academic types..... > I need to figure out which one applies here. Please see: http://www.pantherfilm.com/faq2.html#2_37_01 (which is part of an FAQ that's been effectively untouched for several years. This is not a new requirement). > Between this "problem" and other problems, I am beginning to wonder if > selecting CMIP/CMISE would not have been preferrable... No comment. There's actually no difficulty in implementing this sort of pair of linked tables. Presumably there is some underlying data structure that represents whatever information you are trying to report on? As long as that's kept up to date, you can implement the two tables independently. The fact that they're both working with a shared data source means that the table-within-a-table aspect falls out automatically. Merging things back together again for display at the client end is a slightly different problem. But there's nothing inherently difficult about this - it's just a simple matter of programming. I can't comment about the other problems you refer to, for obvious reasons. Dave ------------------------------------------------------------------------- Take Surveys. Earn Cash. Influence the Future of IT Join SourceForge.net's Techsay panel and you'll get the chance to share your opinions on IT & business topics through brief surveys -- and earn cash http://www.techsay.com/default.php?page=join.php&p=sourceforge&CID=DEVDEV _______________________________________________ Net-snmp-users mailing list [email protected] Please see the following page to unsubscribe or change other options: https://lists.sourceforge.net/lists/listinfo/net-snmp-users
