This site uses different types of cookies, including analytics and functional cookies (its own and from other sites). To change your cookie settings or find out more, click here. If you continue browsing our website, you accept these cookies.
We're actively looking for ideas on how to improve Weekly Challenges and would love to hear what you think!Submit Feedback
Last week's solution is now up - find it here!
This week, we are looking at a few accounts. In this set of data, there are 4 accounts. The first row of every account represents the number of credits/debits against the account, and the second row represents the actual credits and debits paid against the account in the order they were paid. Your task is to find the credits and debits where the sum of debits and credits BEFORE any transaction is equal to the sum of debits and credits AFTER it. Please count the transactions from 0 to match the answer. Below is a picture that illustrates the logic of which transactions should be captured. The picture represents the second account.
Joe, Typo - The challenge start file name says #116, not #117; also the header in the file needs to be correct too.
Because there are <10 accounts, I just used the multi-row tool, but I plan to re-do this with an iterative macro that would work no matter how many accounts there are.
My solution! Practicing my speed-solving for the Grand Prix :)
I like the way that you eliminated the noise that @JoeM inserted into the problem. I also learned from your use of the parse that instead of \s you could literally use a space character. I don't like it, but it is possible.
Good luck in the Grand Prix!
I periodically go rogue on the shortcuts with syntax, though probably not as intentionally as you might think haha... In this case, I didn't even think to use \s. It's been that kind of Monday. You get a gold star for catching onto that though! :)
Do you know why I would object to the use of the SPACE instead of \s?
It surely caught my eye.
BTW, when I was solving this I was using a JOIN with the two sorted streams coming back together. I find your solution more straight-forward.
The space is not as obvious as the \s, for sure - it appears to be nothing, but is in fact something! Can't get anything (or nothing!) past you, @MarqueeCrew!