Important Notice
The pages on this site contain documentation for very old MS-DOS software,
purely for historical purposes.
If you're looking for up-to-date documentation, particularly for programming,
you should not rely on the information found here, as it will be woefully
out of date.
Out of string space (ERR: 14)
■ There are too many string variables for the amount of memory
available. Strings compete with other types of program data
for memory.
■ Possible solutions:
• In the programming environment, unload any documents,
source files, or include files you don't need.
• The "Out of string space" message occurs when any one of
the 64K string segments is filled or when Visual Basic
cannot increase the segment size to 64K. These segments
and their contents are:
String Segment String Contents
══════════════════ ═════════════════════════════════════
Module Module-level string variables
Module-level string array elements
Procedure-level static string
variables
Procedure-level static string array
elements
Named COMMON string variables
Named COMMON string array elements
COMMON Strings in unnamed COMMON
String array elements in unnamed
COMMON
Local string Procedure-level local string
variables
Temporary strings
Local string array Procedure-level local string array
elements (1)
──────────────────────────────────────────────────────────
(1) Note: There is one local string array segment per
procedure. It is allocated when the procedure is invoked
and released when the procedure is exited.
• Find out which of the above string segments is filled by
using FRE(string variable). This returns the amount of
string space left in the segment where the string variable
is located.
• If one segment is filled, you can free up space by moving
a string from the filled segment into another segment.
For example, if the module segment is filled, you can
change a module-level string to a string in unnamed
COMMON.
■ If you need additional help, move the cursor to a keyword
and press F1 to open the Help window.