DrByte:
My post was merely pointing out that EP is not the right tool to accomplish that desired result.
The products use an Auto-incremented ID number - a feature of databases, which ensures that a record that requires a unique identifier, is allocated one.
This facilitates a range of options - one of the more important being to use the RELATIONAL features in a database. Other tables are able to "associate" a line of data against an established field ID - an thereby "relate" to it. This allows for considerable "compression" of information, because instead of having to duplicate (or triplicate, or quadruplicate) a line of data across several tables, one cross-references the tables and fields by using these unique ID's.
In order to ensure that NO "confusion" can exist in this "relationship" process, a database will NOT re-issue, or re-use an ID. In the general scheme of things, an ID "dies" with a record to which it applies, and the value continues to increment numerically.
Truncating a table will reset the Auto Increments to "1".
But beware... you may end up truncating only SOME of the tables which reference the product_id, meaning they are re-set to a value of "1", but you may forget to truncate others where product_id is listed. These will contain the stream of product_id's - so you will end up with one table saying product_id ### relates to "A", and another saying product_id ### relates to "B", or "C"...
This vital "checking mechanism" is rigorously protected in the normal operation of a database, mainly because having conflicts can wreak such havoc.
easypop will not reset this value... hence Dr Byte indicating that the BEST way of ensuring a "clean" database is to start from scratch. The risk of not doing this is considerable.