maybe there is a little misunderstanding here.
It is true that C++ (if used correctly...) manages memory much better than
VB (a language mostly designed for end-users applications), but even with C++ it is NOT a good design to allocate gigabytes of memory! Memory is swapped to disk when there is no more ram available (hard to say when, because windows is a multi tasking system) Swapping makes the application slows no matter which language is used: data is read from/to the disk, that is always used by windows to do its job and all the other applications. And even if you have a terabytes of raid disks windows will always limit the size of your application and the memory you allocate (2GB in XP)
I repeat, this is not a
VB issue: it is programming 101
In 1969 (when most of us were not born yet, I was six at that time and not thinking about programming) we send a rockect to the moon with three men on board. All they had was 16 bits Digital PD11 computer with ~100K of memory, still they arrived (on time) and came back (alive)
Marco
