Working with .dat files

Simple - just use Get the same way you did the Put.

Try this sample code.

I'd recommend explicitly telling VB what you want, rather than relying on defaults. In other words...
Hm... you know, I think we may have a problem here. I'm pretty sure that you have to indicate how many bytes to read when you use Get. In other words, if you wanted to read 5 characters you would do something like this...
For many data types such as Integer, Long etc, this wouldn't matter because they are a specific size. But with a string, I don't know what you'll do. You might need to store the length first. Or instead of using binary format, use Print # or Write # to write in text format, then use Input # or Line Input # to read it back after opening for Input rather than Binary.

Okay I managed to display each individual field, but I had to first declare each field type with it's size, in a seperate module.

I now have no problem's with it, thank you ^_^

..but I know have another question. Whats the code that lets me delete a certain record from a dat file?

Ah, that's not as simple a question as you might think. Changing the data in a file is perfectly simple in Binary mode, as long as the length of the data doesn't change.

To remove part of a file, you basically need to rewrite everything from that point on, and truncate (shorten) the file. Though there are ways to do that, it's basically risky because if anything goes wrong part-way through, you could totally ruin the file. Plus, I'm not sure how you go about truncating the file (though I'm fairly sure it's possible).

The more commonly-used technique is to write a copy of the file without the unwanted piece, then delete the original file and rename the new one. This is how many archiving utilities work, for example (Eg. WinZIP).

Of course, it's also possible to "logically delete" a record. That is, make some change to it so that it is ignored in future. Thus, while physically it is still there, you can consider it as having been deleted. This is actually how a lot of database programs "delete" records, which is why the database keeps getting larger and has to be "compacted" from time to time to remove the old junk.

If you try playing with the search box up top, you'll find this topic has been covered at least once or twice.

Alright! Thank you very much for your time, you've really helped me out a lot.
I did know about logically deleting a record, but I didn't want the files to keep increasing in size over a long period of time.

I think I'll take a look at how to copy to a new file and rename.

Thanks again!

Okay I'm having some trouble with this.

cboSelectCustomerD basically has a list of all the customer names, so I can select a name from the list and choose to delete it.
The code works perfectly when I choose to delete the last record in the file.
The problem arises when I select a record other than the last. It copies all the records I need to the new file, but there's also a gap where the old unwanted record used to be. It's because it's writing to the record number "loopindex". I want the code to write over the gap after it has missed out the record I don't want, I tried several different approaches but I still couldnt get it to work.

Please help =s

.........
Anyone? =<

.........
Anyone? =<

Sorry, it can take a while before anyone has time to look at questions here. We're just volunteering our own time, after all.

It's Monday morning here. I'll try to have a look at this at lunchtime.

I did have a quick glance at the code, and saw what looks like a logic bug. I think in the FOR loop, you need to do the Get every time 'round, and only the Put should be dependent on the If test.

Also, I think (not positive about this) that you should leave out the record number parameter in the Get and Put. In other words, Put #2, , OneCustomer. I've used binary mode a fair bit, but not random mode. So I'm not certain this is the right way to go about it.

See whether this makes any sense, and I'll try to get back to it at lunchtime.

I finally had a chance to read what you actually said about the code, and it seems I was correct. The Get/Put logic is where the problem lies. You need to read all records, but only write out the wanted ones.

Leaving out the record number on the Put should do the trick, if this syntax is valid for random mode. I know it is for binary, but still not sure about random.

Otherwise, just use two counters, one for read position and one for write position. They will both be incremented by one each time around the loop, except that the write counter won't increment when you skip a record.

If performance becomes an issue (in other words, if it's too slow), then let me know. I believe we can make this process much faster with a fairly simple fix, using binary mode instead of random.

I finally had a chance to read what you actually said about the code, and it seems I was correct. The Get/Put logic is where the problem lies. You need to read all records, but only write out the wanted ones.

Leaving out the record number on the Put should do the trick, if this syntax is valid for random mode. I know it is for binary, but still not sure about random.

Otherwise, just use two counters, one for read position and one for write position. They will both be incremented by one each time around the loop, except that the write counter won't increment when you skip a record.

If performance becomes an issue (in other words, if it's too slow), then let me know. I believe we can make this process much faster with a fairly simple fix, using binary mode instead of random.

I know you're using your own time to help others, i'm sorry for bumping the thread like that! It's just I don't have that much time to complete this, I really want to get it done.

I don't think performance would be much of an issue, I'm not going to have that much data stored on my file anyway.
You have solved the problem for me, I really can't thank you enough!! You should really have a rep system for this forum :)

Thanks again!!

Hey, glad we could help. :)