shortening my sequencing records without writing each record

[Kernelpanic]

That's because the functions that operate that type of database are running sub-functions under the hood.

For editing records in QB64, RANDOM access files make it possible to overwrite a record, or make it a null record, without re-writing the file. Most of my office data was accessed with this file format; however, if I wanted to add new records inside of existing records, then I would write a sequential file; otherwise, you would need a function to GET and PUT each out of place record to a new record place. That reshuffling technique is a bit tricky, as I recall.

Pete

Sure, you can do it. I created programs in QuickBasic 4.X that save data sequentially and with direct access. I can't get to the larger one because there doesn't seem to be a program that can convert a QB 4.0x file.

But I printed out some of the source code, and now I've found a direct access file made with QB 4.0x. I have to get my head around how this works under Basic. But it's definitely more work than with MySQL.