Translator 1.135 released
Can be downloaded here
One potential customer noted today that his MDB file does not have a DAO reference, only ADO, and modules, created by Translator does not run. Of course! Same if both references are selected - DAO and ADODB. So now we have explicitly declared recordsets as DAO.Recordset, same for other DAO objects. Translator also detects if DAO reference exists, if no - it display a following message:
"Your application does not have a reference to DAO, which is required to have Translator modules run correctly. Please open any module, go to menu Tools-References and select a "Microsoft DAO 3.6 Object Library" there."
One potential customer noted today that his MDB file does not have a DAO reference, only ADO, and modules, created by Translator does not run. Of course! Same if both references are selected - DAO and ADODB. So now we have explicitly declared recordsets as DAO.Recordset, same for other DAO objects. Translator also detects if DAO reference exists, if no - it display a following message:
"Your application does not have a reference to DAO, which is required to have Translator modules run correctly. Please open any module, go to menu Tools-References and select a "Microsoft DAO 3.6 Object Library" there."
posted by Alex Dybenko | 18:58
0 Comments:
Post a Comment
<< Home