Finally!

 BBS: Inland Empire Archive
Date: 05-08-92 (14:52)             Number: 146
From: MATT HART                    Refer#: NONE
  To: CHARLIE QUANTE                Recvd: NO  
Subj: Finally!                       Conf: (2) Quik_Bas

 CQ> compile as modules, I get 'string area corrupt'.  Question one,
 CQ> do SUBS add quite a bit more to the compile/memory requirements
 CQ> for the program? (Turbo Basic did not support subs in the manner

SUB's must be seperately linked in, but they don't
significantly change memory requirements.

 CQ> QB4.5 does). Question two, how do I avoid the DREADED 'string
 CQ> area corrupt' edit?

Compile your programs with /D and find the real problem.  You are possibly
using far too much string space - look to moving some out
to far memory as fixed length strings or TYPE structures.

 CQ> Question three, Survivor! loads in a large
 CQ> sequential data file, and seems to take FOREVER.  I saw a method
 CQ> for saving a sequential integer array using BLOAD BSAVE, but it
 CQ> was for a one dimensional array.  Is a similar method available
 CQ> to save multi-dimensional arrays?

This is the same as for multi-dimensional as for single dims.  You have a 64K
limitation though, which can be somewhat overcome by using
two BLOAD/BSAVEs.

 REDIM Array(100,100)    ' Note that this is actually
                         ' Array(0 TO 100, 0 TO 100)
 NumBytes& = 101*2*101*2
 DEF SEG = VARSEG(Array(0,0))
 BSAVE "ARRAY.BIN",VARPTR(Array(0,0)),NumBytes&
 DEF SEG

 Bload is the same - without the NumBytes&.

I'm not a door writer, so I can't help you with you fourth question.
---
 * Origin: Midnight Micro!  V.32/REL  (918)451-3306 (1:170/600)