> > > There is no need for a primary key in a one-tabled database. > > > > You'll need some way to determine what makes any individual > > record unique, or your data won't be worth very much, even > > within a single table. > > I looked. Approach must do something internally. It's not really > a database, but a flat-file application. Only one table per file. > Filemaker Pro uses (or used) a similiar implementation. I think you misunderstand my intent. The database may certainly allow you to create tables without specifying the primary key within the database schema. But, for the table to be useful to you, there has to be some criteria for uniquely identifying each record within the table. Otherwise, you'll have no way of determining whether a record is a duplicate or not! This is a common problem in flat-file databases, where the application using the database didn't have any logic to determine how to handle record uniqueness. As a result, when you look at the data, you end up finding a lot of garbage data, and it's difficult to programmatically differentiate the good from the bad. Dave Watts, CTO, Fig Leaf Software http://www.figleaf.com/ voice: (202) 797-5496 fax: (202) 797-5444 ------------------------------------------------------------------------------ To unsubscribe, send a message to [EMAIL PROTECTED] with 'unsubscribe' in the body or visit the list page at www.houseoffusion.com
