At 14:02 16/09/2008 +0200, Joe Grech wrote:
In fact I am using 2.4.1 and my table has a primary key which I can't figure out why has lost count with the real record increment i.e entering record # 20 and the primary key shows 30 or so. I change it manually to correspond with the record but reverts to the original count when entering a new record.
As I've probably said before, I'm no database expert, but I may be able to offer an idea here.
You have two alternatives when it comes to choosing a primary key: to use an existing field as your primary key or to let Base create an additional one. In the first case, you should have no problem editing the values in that field, providing you never attempt to duplicate a value there.
In the second case, you shouldn't be thinking of the primary key field as being part of your data, but merely an artifice that the database needs in order to index your data. It makes sense for this to be set to provide a value automatically (as it seems you have done), but only because the values there should not matter to you. If you need to make use of consecutive numbering of your records, you should create an additional field for this purpose and not expect Base's efforts to do this for you.
I trust this helps. Brian Barker --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
