FiveTech Software tech support forums

chatGPT proposal: Topic ID: A unique identifier for each help topic. This field can be an auto-incrementing numeric value or a GUID (Globally Unique Identifier) that serves as a primary key for the table. Topic Title: The title or heading of the help topic. This field ...

You need to use relational databases like this:

ITEMS.DBF
ITEMID <---primary key (auto incrementing)
DESCRIPTION
CATAGORYID
BRANDID

CATAGORY.DBF
CATAGORYID <--- primary key (auto incrementing)
CATAGORYNAME

BRAND.DBF
BRANDID <--- primary key (auto incrementing)
BRANDNAME

... to write, the better. Less chance of errors, faster, and easier to read. If you use one of the above, you don't have to write any code to get auto-incrementing primary-key values. James NOT RUN TAUTOINCREMENTAL I NOT SEE SYSFILE:DBF WHERE IS the FILE Sysfile.dbf you se eit ? where https://i.postimg.cc/L6KGd5vm/gggg.png

... to write, the better. Less chance of errors, faster, and easier to read. If you use one of the above, you don't have to write any code to get auto-incrementing primary-key values.

... issues or potential issues. I may take another look at it myself, since you have pointed out that you can APPEND FROM without getting automatic incrementing. That was a show-stopper for me before I knew how it worked. James

... database, or IDs out of sync. Not possible. These RDDs are very reliable. You still can't reuse deleted records, though. I do agree that auto-incrementing ID's is very useful, in fact indispensable, and I have always used my own system of doing this. And since I can replace the ID field, I ...

... could APPEND FROM duplicate IDs into an existing database, or IDs out of sync. You still can't reuse deleted records, though. I do agree that auto-incrementing ID's is very useful, in fact indispensable, and I have always used my own system of doing this. And since I can replace the ID field, I ...

As I mentioned, if you use it you cannot reuse deleted records because the autoincrementing field cannot be changed. Also, if you need to change the file format, you can't just export it, change the database structure, then import that data again because the new ...

... What is exactly the problem with this extended type. This week I was reading about this and I was thinking in use DBF with this + type. Auto-Incrementing is normal that can not be changed. Another feature that I am thinking is about the PASSWORD to protected the dbf. Do you think that is ...

Silvio,

I recommend that you not use the + type (auto incrementing) due to some issues. One problem is that you can't reuse deleted records (because the auto-incrementing field cannot be changed). Do a forum search for "auto incrementing" for more information.

James

... * TGET: - Extension to SPINNER clause. SPINNER BUTTONS <cbmp1>,<cbmp2> displays two buttons on left and right for decrementing and incrementing the values. If cbmp1 or cbmp2 or both is/are empty, default bitmaps are provided. Each button's width is equal to the height of the Get. ...

Antonio F. Thanks for confirming that. I have been meaning to ask about it. So, it seems, that my original auto-incrementing system should still work with the ADORDD. I will do some testing to confirm it. Using the ADORDD is too easy, where's the challenge? ;-) Keep working your ...

How is this different from an auto-incrementing field? Is it a date/time field? Does it have the same issues as an auto-incrementing field (the possibility of being renumbered)?   No, it is totally different than an auto-increment field. Yes, ...

... that DBFs had auto-increment fields until a few months ago, so I have not been using them. I have my own database class that does it's own auto-incrementing using the method I mentioned in the post above. I always put the primary key into the first field so I can use the same code in my database ...

... a sequential number? I'm sure there is one, I just don't know what it is. (3) implement a row version field. How is this different from an auto-incrementing field? Is it a date/time field? Does it have the same issues as an auto-incrementing field (the possibility of being renumbered)? 4) keep ...