Thank you for your feedback, Sunet! I realized that my reasoning behind this decision wasn't clear so here is the longer explanation since it does warrant some backstory (and perhaps someone could think of a solution to my dilemma!).
The demo works by having the user type in a value for one of the measurements and then it will show a layer with a number variable that is multiplied by the number entry. So for example, the learner can type "1" under "Tablespoons" (the number entry), and this is multiplied by number variables I added in Storyline (variable named "TbspToTsp" = 3; variable named "TbspToCups" = 0.06), which would appear in a layer once the user stopped interacting with the number entry box.
I found that while most of the calculations were accurate, Storyline would round the numbers in a way (up to the hundredths place) so that there were some large inaccuracies in the calculations, particularly when I was converting from grams to cups. Since there are 201 grams to a cup, this means that there are 0.00498 cups to one gram, and Storyline rounded this number to 0. I couldn't make the number variable that multiplied to the number entry a zero because it would then say that X grams equaled zero cups, hence why I only made that conversion go only one way.
I provided the Storyline file to my demo in the Review link (see the comment sidebar) if anyone wants to play around with it and perhaps find a way around the decimal rounding. I saw a few threads that talked about using Javascript but I'm afraid that I know next to nothing about that.
I know that these numbers are also dependent on the ingredient and they just came from simple Google searches, so please take these conversions with a grain of salt (pun intended)!