Walter Meester
HoogkarspelNetherlands
General information
Category:
Databases,Tables, Views, Indexing and SQL syntax
Gary,
In addition to what Evan and Craig said, the real problem lies in the fact that DELETED() records are still stored in the table. This is exclusively (that I know of) a xBase problem.
I'm not that fond of using generated key's in every table (though it has got its use in most tables). I believe there are cases where generated key's do not make sense at all, So if you think you've got a good reason to use a intelligent primary key, the best you can do is add a index filter 'FOR NOT DELETED()' and add another regular index on the same expression without a filter to take advantage of rushmore.
Walter,
>How are developers handling the problem where a primary key and data record is added to a table. The user decides to start the record over so they delete the record. When they start to add the record again with the same key, they will get a duplicate key message because the key, although deleted, is still in the index, until I pack the file. One idea would be to change the key when I delete the record. Is there a better approach anyone is using.
Previous
Reply
View the map of this thread
View the map of this thread starting from this message only
View all messages of this thread
View all messages of this thread starting from this message only