Store Code -- Alternatives Wanted

I'm looking for feedback on how others store code and why they store it the way they do. As I see it the Advantages/Disadvantages of the various methods are:

VB Code:

A.  Use a program such as CodeBook.
 
      Advantages
 
      1.  Code all in one place
      2.  Listbox is available for a sorted list
      3.  Search routine to look for code
 
      Disadvantages
 
      1.  Stored in a separate file (normally DB) so subject to corruption.
      2.  Code must be formatted according to CodeBook requirements
      3.  Lengthly code examples with multiple functions/subs are not easily handled.
 
 
B.  Store as a BAS Module.
 
      Advantages
 
      1.  Code all in one place (Module)
      2.  Listbox is available as built into VB
      3.  Search routine to look for code (VB)
      4.  Stored as text
 
      Disadvantages
 
      1.  Lengthly code examples with multiple functions/subs are not easily handled since they not kept together (eg. events)
 
C.  Stored as  separate files on HardDisk
 
      Advantages
 
      1.  Code all in one place
      2.  Search routine to look for code (Explorer)
      3.  Can be Stored as text or zip or whatever format
      4.  Lengthy code examples can be kept together
 
      Disadvantages
 
      1.  Large number of small files which uses up a lot of HD space.

Quote:

---

Originally posted by dw85745


<snip>

C. Stored as separate files on HardDisk

Advantages

1. Code all in one place
2. Search routine to look for code (Explorer)
3. Can be Stored as text or zip or whatever format
4. Lengthy code examples can be kept together

Disadvantages

1. Large number of small files which uses up a lot of HD space.

---

that disadvantage can be overcome by using zip files (if you're using windows xp, anyway, because explorer treats zip files like a folder... this eliminates the many small files and the associated 'cluster size' issue that causes many small files to clog harddrives.

Agent:

Thanks for response. Using the harddrive has always been my preference but never liked the wasted slack space due to cluster size.

I am interested about your comment

--------
because explorer treats zip files like a folder...
---------

If has always been my understanding that folders (directories) are handled the same way as any file. Yes -- I know they are kept tract of by the FAT, BUT I THOUGHT each folder/directory took up the same cluster size as any file (eg. 1 byte file = 1 cluster).

Am I in ERROR?

How about using this codetree. It is created by Rick Bull, and it works great!

You can store all kinds of code in it, nicely sorted into subsections.

Thanks for the reference. Will take a look see.
What I'm really interested in is WHY (Advantages/Disadvantages) you made re the decision to use a separate program to store your code instead of just using the harddisk and accessing using explorer.