You can also delete the record and/or database when the game is finished, if you were worried about taking up too much space.
Nick "Brian Atkins" <[EMAIL PROTECTED]> wrote in message news:100501@;palm-dev-forum... > > First, if there is a FAQ item, or guide, which addressed > this, please point me to it. I couldn't find anything > specific to my needs. > > I am working on porting an old dos utility to help play > the old Rail Baron board game. I am using the Preferences > facility to store player and game state information as > illustrated in the SDK Hardball example. However, this > game can result in a lot of "turns". I would like to store > the history of each players turns (trips, actually, with > source and destination and payoff information but am unsure > how best to do it. > > Since the number of trips each player may do in the course > of a single game is quite variable, I wanted to use some > dynamic memory mechanism rather than a static array, with > the potential for overrun, etc. > > Since I need to keep this information as part of the game > state, to enable the game to be suspended while other Palm > apps are run, I need to provide some sort of persistent store. > This data is only relevant to a single instance of the game, > however, and I do not intend to support multiple, simulations > runs. When the user selects "New Game", all old player and > game state and player trip information needs to be erased. > There is no persistent information at all (no high score, > for example. > > Should I put the trip data into a record database? That > seems rather heavyweight for what I need, since it only > needs to remain intact during the life of a single game, > and will never be synchronized, backed up, etc. > > What other alternatives are there? I am still quite new > to Palm programming. > > Thanks! > Brian Atkins > > > -- For information on using the Palm Developer Forums, or to unsubscribe, please see http://www.palmos.com/dev/support/forums/
