Ick tables. Sometimes they are necessary, but they are painful. I used tables in Characters which can be found at http://writerbenjamin.com . It is basically a clone of the Address book contacts, but it is for story characters so all the fields are different and I have more user defined fields. NaNoTrack also uses tables, but I did not base it on anything. Both needed tables to work. E-mail me at [email protected] for the source code. Characters was actually adapted from Foster's Library code because I found the Addressbook App too confusing.
Looks like you need a table from your description. If you can write it without a table, it would be easier. I hate tables, but they must be done in some programs. Base the program on Foster's code if you have to. He allows its use in your code. My code is overly complicated because I wrote it for the Alphasmart Dana, the Handera Pro, and the Palm T|X and had to write for three different non-standard screen resolutions. Still the table code should be the same. Benjamin http://writerbenjamin.com Luc Le Blanc wrote:
I have to design a form where I want 8 rows of 5 columns, 3 of them being editable fields, the other 2 being a checkbox and a user-selectable label (hopefully a selector trigger). The total number of rows (about 30) is to exceed the screen, thus requiring scrolling. Do I gain anything using a table object instead of 8 checkboxes, 8 selector triggers and 24 field objects? I read Foster's chapter on tables, and I'm still unconvinced, as tables seem to require even more code (esp. callbacks). Luc Le Blanc
-- For information on using the ACCESS Developer Forums, or to unsubscribe, please see http://www.access-company.com/developers/forums/
