The database entries themselves have no limit, only their elements (properties).
To be clear on how a database is intended to be used, let me give an example.
Lets say you wish to have a list of items, you would (most likely)
call your database 'Items'.
Each entry would then be a separate item, no limit to the number of
entries. As an example: Mana Potion and Health Potion.
The elements are the various aspects or properties that every entry
(item) on this list will share, such as Cost, Power, UseAbleOnMap.
The above example would provide you with a database that looked
something like this:
Items
> Mana Potion
>> Cost 20
>> Power 15
> Health Potion
>> Cost 10
>> Power 25
To need more than 30 elements, you would need to have over 30
different properties for your items to have (no game I have seen in my
life has this many), in fact I have rarely found a game that exceeded
5.
If you are using elements to store information such as a list a
players that have this item, or a list of skills a player may have,
there are other methods, if you are dead set on using a database for
this purpose, you could, for example use a single element to store a
comma separated list, and using various expression commands to read
the list.
> --
> You received this message because you are subscribed to the Google Groups "RPGds" group.
> To post to this group, send email to rp...@googlegroups.com.
> To unsubscribe from this group, send email to rpgds+un...@googlegroups.com.
> For more options, visit this group at http://groups.google.com/group/rpgds?hl=en.
>
>
--
If you make something that any idiot can use, only idiots will use it.