Elliot,
The duplicate ID number problem is unique to Links 2.0, and flat files. It's somewhat impossible with Links SQL, since the ID field is an auto-increment field, and as such is defined as _unique_.
Additions grab the next available ID number (that is what the ? is for), and insertions should also use a ? for the ID field, or risk getting an error message "Duplicate Key" or "Duplicate Field Value" or similar.
Using an auto-increment field is probably the best way to guarantee each record in a database has at least one UNIQUE identifier, and it satisfies the rules for normalizing tables.
http://www.postcards.com
FAQ: http://www.postcards.com/FAQ/LinkSQL/
The duplicate ID number problem is unique to Links 2.0, and flat files. It's somewhat impossible with Links SQL, since the ID field is an auto-increment field, and as such is defined as _unique_.
Additions grab the next available ID number (that is what the ? is for), and insertions should also use a ? for the ID field, or risk getting an error message "Duplicate Key" or "Duplicate Field Value" or similar.
Using an auto-increment field is probably the best way to guarantee each record in a database has at least one UNIQUE identifier, and it satisfies the rules for normalizing tables.
http://www.postcards.com
FAQ: http://www.postcards.com/FAQ/LinkSQL/