General information
Category:
Coding, syntax & commands
>Thanks for the response. It is still helpful to find out that something cannot be done (at least easily), so i'm off trying to find the solution.
>
>I can see why it is easier to use one-to-many table solutions rather than a spreadsheet like approach, which is what i've been doing (ie a table with fields lname, phone1, phone2, phone3). one-to-many is much more flexible. but now that i want to put this information into a grid or listbox where people can see each contact with all their information in one row, i'm wondering about it. but the flexibility with design does make the initial part much easier.
I'd think about an alternate interface for this data. Since you don't know how many phones any one person might have, a single row isn't really a good way to look at it. Something like a paragraph with the name above and the list of phones indented is a better choice.
Actually, a really good alternative here is a treeview with the person as a parent and each phone type and number as children.
Tamar
Previous
Next
Reply
View the map of this thread
View the map of this thread starting from this message only
View all messages of this thread
View all messages of this thread starting from this message only