Path: utzoo!attcan!uunet!cs.utexas.edu!titan!drack From: drack@titan.tsd.arlut.utexas.edu (Dave Rackley) Newsgroups: comp.sys.ibm.pc.misc Subject: Re: Question on "string space corrupt" errors in Quickbasic Message-ID: Date: 11 Oct 90 16:29:56 GMT References: <90284.091355F0O@psuvm.psu.edu> Sender: news@titan.tsd.arlut.utexas.edu Organization: Applied Research Laboratories, University of Texas at Austin. Lines: 37 In-reply-to: F0O@psuvm.psu.edu's message of 11 Oct 90 13:13:55 GMT >In article <90284.091355F0O@psuvm.psu.edu> F0O@psuvm.psu.edu writes: > Lines: 15 > Hi netters! > I've been using QuickBasic 4.0 for writing some data collection > programs using the Keithley Quick500 resident software. Every now and > then, These "string space corrupt" errors will rear their ugly head. > I've been trying to determine if it is the fault of QuickBasic or > Quick500. > On my program, I know I'm not doing any PEEK or POKES, and I'm not > sharing variables across modules; so I shouldn't have a mismatched COMMON > problem. > I would like to hear from anyone who has run into the "string > space corrupt" error, and how you solved the problem. I'm banging my > head against the wall! > [Tim] I once saw a similar problem, using QB 4.0. My problem hinged on the fact that I was using variable length strings, exclusively. My solution was to dimension strings to a fixed length before passing them as arguments. See your reference guide under the DIM topic. Hope this provides some insight! :-) -- DISCLAIMER? I don't know anything 'bout any ol' disclaimer! +=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=+ | David Rackley | | | Applied Research Laboratories | Remember, you can tuna fish, | | The University of Texas | But you can't tuna piano! | | Austin, TX. 78758 | | +=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=+