Depending on the structure of your code you could use #include statements:

#include "MyFile.sbas"
 

which will act as though the code in that file were simply inserted wherever the #include statement is. Combining #include statements with subroutines or functions in the global code area gives you a lot of centralized reuse, even across multiple applications.

No, you probably want to place the #include statement in your code where ever you have code that repeats and you want to be able to edit it from just one file.

In your included file (let's name it "greet_john.sbas"):

if(@User() = "John")
{
    writeln("Hello John")
}
else
{
    writeln("What happened to John?")
}
 

Then in any code that needs to greet John:

#include "greet_john.sbas"
 

Wherever you place the #include, the text from the file named right after "#include" (in this case "greet_john.sbas") will be inserted. That way, you can write the code once and use it in many events or even many applications, and edit it from a central file.

You can specify either a complete or relative path to the file. If the path is relative, it is relative from the "Start In" directory specified in your icon. So, if your "start in" directory is: "C:\Users\NHUser\Sesame" and you specify "#include MyInclude.sbas", then the file, it will insert will be:

C:\Users\NHUser\Sesame\MyInclude.sbas

The .sbas extension is completely optional, but it stands for "SBasic". The file does need to be a text (ASCII) file containing valid SBasic source code.

All it really does is insert the contents of the file into your SBasic program right at the point where the #include statement is in your code. If you do go this route, remember that all of your client computers will need a copy of the included file, always in the same relationship with your "start in" directory.