The first shall be last, last shall be3 first and all that, so Mike, you're up...
> I don't understand why you do that "MyArray[75]['red']" instead of > "MyArray[75] = 'red'" - maybe it's obvious, but I have never seen > anything like that before. It's because of the level of abstraction for my form building thingie. I have forms in one table, form fields in another. Some form fields can be drop-down lists, and some have multiple dependant drop down lists (Country / City / State type of thing). I have one template for the defining of all form fields, and one for the presentation of all form fields. As I am defining the form fields, I am looping, and looping, and whoa! I come across a drop down list. So if the drop down list is based on multiple dependent drop down lists, I need to capture what I am going to call these drop down lists. So I say MyFormField[FieldID][1] = MyFieldName1 and MyFormField[FieldID][2] = MyFieldName2. Now Gary's turn... > 1. why dont you just... store the query and then re-query the query (we do > that) > 2. why dont you just... create a struct and use the ID as a key in that > struct and then > store the rest of the data as a struct under that key (we do that too) 1. Because I want to try to avoid defining queries in my presentation layer. I may have to give in and do query of queries, but hope not. Just my own framework. 2. Looks interesting, I will have a play, thanks! Chad who was very cold from 5:30am to 7:30am yesterday broken down on the side of the road --- You are currently subscribed to cfaussie as: [email protected] To unsubscribe send a blank email to [EMAIL PROTECTED] Aussie Macromedia Developers: http://lists.daemon.com.au/
