>>You can use WinDrawChars to draw anywhere within the current draw window, so unless you change the draw window or the Table Manager has changed the draw window (and you can always change it to anything you want anyway), you can use it to draw in the second column. However, if the second column is editable you will get very undesirable results if the user taps anywhere in the second column while you have drawn on it. So if you want to try this you will also have to change the second column to not editable with FldSetAttributes() for any rows where you have drawn over two columns. This all seems quite messy to me, so you might want to think about doing something else<<
Thanks for the further comments... I changed the code to use WinDrawChars() in the first column, and it paints into the second column as I want it to. But, when I get the TableLoadData() message for the second column in the same row, the field paints over what I just drew, but _only_ in Palm OS 3.5!! (I set a breakpoint to stop after painting first column but before second column's TableLoadData() call to confirm this) When I get the TableLoadData() call, I do set most of the field's attributes to false (editable, usable, visible, dirty, no underline). I even tried changing the field's bounds to see if that would have any effect. I've looked at the ROM source code quite a bit now to see what table and field controls do, and I can't fathom why the field is drawing when I've set all the related attributes to false! I'm wondering if the Table or Field controls have changed for Palm OS 3.5 and if the ROM source code I have does not include these changes. Sigh... -- For information on using the ACCESS Developer Forums, or to unsubscribe, please see http://www.access-company.com/developers/forums/
