Jason, so sorry I didn't catch your earlier post! I'm still at a bit of a loss as to the origin of the error. Unfortunately, the screen resolution fix didn't end up resolving the error screen. The error has only impacted that single study so I *think that it might be specific to my coding. I'll let you know if it pops back up or if I determine the source!