Without your DB there isn't a lot we can do to help you, but two things do spring to mind.
1) Never concatenate strings to build a SQL command. It leaves you wide open to accidental or deliberate SQL Injection attack which can destroy your entire database. Always use Parameterized queries instead.
When you concatenate strings, you cause problems because SQL receives commands like:
SELECT * FROM MyTable WHERE StreetAddress = 'Baker's Wood'
The quote the user added terminates the string as far as SQL is concerned and you get problems. But it could be worse. If I come along and type this instead: "x';DROP TABLE MyTable;--" Then SQL receives a very different command:
SELECT * FROM MyTable WHERE StreetAddress = 'x';DROP TABLE MyTable;
Which SQL sees as three separate commands:
SELECT * FROM MyTable WHERE StreetAddress = 'x';
A perfectly valid SELECT
DROP TABLE MyTable;
A perfectly valid "delete the table" command
And everything else is a comment.
So it does: selects any matching rows, deletes the table from the DB, and ignores anything else.
So ALWAYS use parameterized queries! Or be prepared to restore your DB from backup frequently. You do take backups regularly, don't you?
2) That's some weird code: you appear to be using
$applied
as both an ID
$updateStr = "select... where ce.uid ='$applied'";
And as a mathematical value:
$updateStr = "INSERT INTO ... VALUES (('$applied' - ($applied - $totalArray[gross_total])), '$applied')";
But that's made even weirder because
'$applied' - ($applied - $totalArray[gross_total])
will always be
$totalArray[gross_total]
anyway ...
I'd strongly suggest you start by thinking about what you are actually trying to do, and where things are stored! Then use the debugger to follow what your code is doing when it runs and watch what values to read / pass / end up with.