I finally found the resolution in a Microsoft Tech Support article - it is a ODBC driver problem, not an iPronto problem. I followed the instructions in the Microsoft Knowledge Base Article - 324520, reinstalled the iProntoEdit SW and all is fine. Here's the link.

[Link: support.microsoft.com]