> > structure usually makes more sense. If, on the other hand, you're
> > trying to describe a bunch of items together, an array usually makes
> > more sense. If you want to describe the attributes of each item
> > within an array, you can create an array of structures.
>
> OK... so in the case I have... a form where a client enters cassette
> reference material into a form (each cassette has 4 attributes... issue
> no., cassette title, date and publication title) an array would appear
> to be better since there would be upwards of 25-30 cassettes entered at
> one time..no? Haven't played with structure yet, so ..
If you have a bunch of items (cassettes), it makes sense to store them in an
array. If you have things that you want to associate with each cassette,
that cassette should be described as a structure. So, it sounds like an
array of structures is a good way to describe your data.
Dave Watts, CTO, Fig Leaf Software
http://www.figleaf.com/
phone: 202-797-5496
fax: 202-797-5444
[Todays Threads] [This Message] [Subscription] [Fast Unsubscribe] [User Settings] [Donations and Support]
