Qbasicnews.com

?
Does it mean I have to split my programs to modules?

Out of string space = memory problems. So yes. You may also have to compile from command line.

General advice: when you start a new program, split it in modules from the beginning.

Splitting into modules won't really help with out of string space errors.

If you're using qb 4.5, you have 64k of string space, some of which is used by qb. The rest is easy to fill with a few string arrays...

Try to use less strings.

You can use FRE("") to see how much string space is free.

My advice:
1. Dump Qb 4.5
2. Adopt Qb 7.1
3. use the /es/ah options with it
4. Split your code into modules(Learn the COMMON SHARED command)

http://faq.qbasicnews.com/?blast=PushingTheLimitsOfQb

here's nathan's tut to split ur code into modules :bounce:

Quote:Dump Qb 4.5
Adopt Qb 7.1

What? You trying to advice him using QB71? Since this module splitting has nothing to do with QB71 I don't really understand what he should do with QB71. If he uses QB45, let him use it.

But as for the question, run QB with the /ah option and split it into modules. For this, you can refer to, indeed, NaThan's article. http://faq.qbasicnews.com/?blast=PushingTheLimitsOfQb. Furthermore, avoid using strings for operations where strings can be avoided.

mmmmhhhhmmmm....

Quote:/es/ah

qb 4.5 doesnt allow moving strings to EMS :lol:

ahemmm.... just use my neoEMS module, allowing EMS for QB. Or use my neoVXMS for (Virtual) XMS in QB.

Show Off =)

They're done, but I can't release them yet (first need beta-testing). But if NeoLib is released for QBCPC and for public it's gonna be great!

You mean that he cant use your modules rightaway?