It ended up being a simple need to just log out of ProConnect and then log back in. Tech support said that sometimes a reboot of the software does the trick, to clear out cache, etc.... Thanks for chiming in.
View solution in original post
