So I'm making a bound and control map and I have two problems.

1. At the beginning of each round, it displays the text of what enemy units are next. It was working fine for a while, but after getting to make the 20ish scenarios,while playing, it started to display random strings of data from the game, such as force names, switches, and comments. Does anyone know how to fix this?

2. Is it possible to create scanner sweeps? I tried but it doesn't seem to work.

Thanks all

1. Your strings got corrupted. Did you go over 1024 strings? Revert to an older version. ScmDraft's backup database is very helpful in that regard.
2. No.

Keep in mind you can put multiple lines of text in one string. There is no way you can run out of strings after only 20 scenarios. Deleting strings with the string editor causes string indices to get all messed up (with the same effect as what you described) and is usually only done to create crashbanning systems. Never touch "New String" or "Delete String" unless you know exactly what you are doing.

Also, you can force computers to scanner sweep if a unit of theirs is attacked by a cloaked NORMAL unit (meaning no heroes like zeratul/kerrigan, has to be a melee unit) in a certain location, if they own a comsat station and have at least enough energy to scan. Simply give shared vision for about 55 hyper'd deaths after you create the units to force the comsat sweep.

Note that shared vision will only update every 50 hyper'd deaths (cloak detection every 15), so if you want to see the area, you should create a map revealer first, then remove it for the player.

It says I've used 378/1024 strings. I haven't done anything with the strings section. It got even worse when I got to the 30s.

For the 2nd problem I'll just create a temporary observer.

If you feel like mucking up a bit, you can fix the strings manually by editing the "display text" actions in the triggers to refer to the correct string. Starforge can do this if you edit actions.lst to have:
Action DisplayText(Number Text, Number AlwaysDisplay)
in it. This way you display the string number instead of the actual string in the trigger (triggers do not store strings, they store a pointer to the string).

Otherwise, revert to and older save, or simply edit the strings in the triggers to say the correct stuff.