1. Change all "byval index as long" to "index as integer" which should half the memory consumption for all that.

2. Change lcase(parse(0)) = "
to case

3. In type recs or even anywhere unless you are going to have more than 32,000 of something change from long to integer which will have the amount of memory it takes up.

4. Change all booleans to byte and use 0 and 1

5. Even better if you use the bitfield system (just search it) *props

6. If you are always going to get a value between 255 and 0 then change longs or integers to byte. that should decrease that memory consumption by down to 1/8th

8. if you use exit sub anywhere its easier just to use select case.

7. Don't use fixed length strings e.g "* MAX_LENGTH" just remove it you dont need it. if you want a max character property change that in the textbox properties.

Yeah, that would work.

Change it to Byte instead

It has proven that no speed change occur.

Nothing in MS requires anything to be above 32000. So not sure if that is a good idea

Hum?

Isn't the difference between byte and long 2bytes or something?

If you don't make a string fixed length, it uses 20 bytes + the string length MORE memory. Keep all the strings that you can fixed length.
Actually fixed length strings cause problems

No in vb6, byte = 1 long = 8

Yes you would be right if everyone were to fill in all the spaces but...

Fixed-length strings are generally slower than conventional strings, because all VB string functions and operators only recognize conventional strings, thus all fixed-length strings must be transparently converted to and from conventional strings.

I also believe we prooved a while back that integers are slower than longs in some situations. Moral of the story: Depending on what that variable is doing, Long may be a better option even if it is too big.

However, Visual Basic does provide an unusual "Currency" Data Type, which is essentially a 64-bit fixed-point number with 15 digits to the left and 4 to the right of the decimal point.