Oh yep, I didn't catch the dgindex check for the first one. ###### yep, dgline is the way to go. I am not sure that you can assume that dgIndex of me = 1 is equivalent to dgLine of me = 1. So I think the line: If the dgindex of me = 1 then
needs to be: If myPosition of me = 1 then or if the dgLine of me = 1 then ######## As for which way to go (indexes vs lines) the datagrid api says this about them. *dgIndexes* - get the dgIndexes - Returns the internal list of indexes in the order in which they appear in the data grid. Indexes are the numeric indices used when setting the dgData property. *dgIndexOfLine* - put the dgIndexOfLine [ pLine ] - Returns the index associated with the given line. Since the button that generates the data doesn't generate in alphabetical order, when the dgdata is set and then sorted by the first name key, the internal array is still in the order that you generated it, but the lines are the order of appearance. The physical line number displayed in the datagrid. (basically the same thing you said above but applied to the line comparison to determine header visibility) To paste scripts and have them show up right you might set your client to send plaintext rather than html, or use an intermediate paste. Paste into notepad or something, then reselect and copy and paste into the email. Pretty sure you're correct about the reasons behind the list rejection. I'm sure there are better methods though. _______________________________________________ use-livecode mailing list use-livecode@lists.runrev.com Please visit this url to subscribe, unsubscribe and manage your subscription preferences: http://lists.runrev.com/mailman/listinfo/use-livecode
