OK, I had no idea what you were talking about when you tried to re-explain what I said, so I'll assume you didn't understand. These errors are almost certainly created by dynamic code that is being given dodgy variables, such as:
_frog = 10;
call compile format ["_fish = %1", _frog]; // The string is formatted to "_fish = 10", which is then compiled and run, setting the value of _fish as expected.
However, when doing this sort of dynamic code translation, errors are easy to introduce:
_frog = 10;
call compile format ["_fish = %1", _treeFrog];
Since _treeFrog is undefined, the string is formatted to "_fish = schalar bool array string oxe0ffffef", which is nonsense in SQF and causes an error when it is compiled (though "_fish = schalar;" would make sense and is why it suggests you might have missed out a semi-colon at this position).
The problem with "<Null-object>" is similar, and is caused by compiling a string that contains an object that is null (probably caused by the object having being deleted beforehand). The example code isn't realistic, just being a simple example to explain a point:
// soldier is a game object that has been given a name in the editor.
deleteVehicle soldier;
call compile format ["_fish = %1", soldier];
Since soldier is null after it has been deleted, the string will be formatted as "_fish = <Null-Object>" which is again gibberish to the compiler and causes an error. If soldier hadn'y been deleted, it would be formatted as "_fish = soldier" which would have run correctly.
Ultimately though, we can't debug code that we can't see, except to give general guidelines as to what might be causing the error. If you don't understand exactly what the code you are running does, then you will usually find it very hard to debug, even given plenty of advice from us (unless it is an general problem like forgetting a semi-colon). You are using a number of scripts together, as well as code that we have given you in this thread, as well as your own code to glue it all together... The error could well be in any part of this melange, including something in SPON Money or the SPON Money demo, or due to an unexpected interaction between scripts or your changes to them. At this point, you probably need to attach the full mission for us to look at, since anything could be going wrong at this point (and anything involving dynamic code is usually harder to debug).