When someone shares a script with another person and that shared script has
includes there is a small problem. Or the same problem occurs if you move an
include script to another folder on your machine.

When the .sb7 file is loaded and you go into the script editor you see a tab
for that include script. If you try to edit that script (by clicking on the
tab) you get a message that it cannot be loaded. The problem is that I (as a
new user of sb7) didn't realize that the tab was empty and would not be
loaded until I actually clicked on it. I thought the tabs came from the
folder on the disk because the names on the tabs exactly matched with what
was in the Include folder on the disk.

I later realized that the problem was the include in the .sb7 file. It
needed to be changed to the true location before I could click on the tab and
get the include to edit.

Suggestion: When parsing the .sb7 file for includes give a warning message
that the include is not found and put the tab up with an *error* indicator
next to the name or in some way flag the source include stmt that it is an
incorrect location.

Thanks, Bob Roos