Skip to Content

DAO Error Code: 0xd0f Source: DAO.Fields

we have a vb6 app that working with CR 10.

Newly after last windows 10 updates, including KB4480966, we cannot open our reports getting this error:

DAO Error Code: 0xd0f

Source: DAO.Fields

Any ideas how to fix the issue with these windows updates?

Thanks

Add comment
10|10000 characters needed characters exceeded

  • Follow
  • Get RSS Feed

9 Answers

  • Best Answer
    Jan 10 at 02:51 PM

    DAO is no longer supported by a lot of programs.

    Work around is to convert your reports to use ODBC.

    Don

    Add comment
    10|10000 characters needed characters exceeded

  • Jan 10 at 05:19 PM

    thank you for your attention.

    We have handreds of report and need to convert them ASAP.

    Could you please give me a link or some advise how to do it?

    Add comment
    10|10000 characters needed characters exceeded

  • Jan 10 at 05:29 PM

    OK, I suggest contacting or looking on Microsoft's site what that error means.

    TTX files are 32 bit only and uses the DAO engine so try installing the Office runtime, you'll have to check what version to use. It should update or install the 32 bit DAO engine.

    Then look at converting all of your reports to ODBC.

    Also, VB 6 has not been support by MS for a very long time.

    Time to upgrade to .NET and CR for VS:

    https://wiki.scn.sap.com/wiki/display/BOBJ/Crystal+Reports%2C+Developer+for+Visual+Studio+Downloads

    Don

    Add comment
    10|10000 characters needed characters exceeded

  • Jan 11 at 06:47 PM

    Soory no idea, VB 6 eand of life as well so no idea what parts it's going to use to connect to Access.

    Search MSDN for any known issues with MS patches that break DAO.

    Add comment
    10|10000 characters needed characters exceeded

  • Jan 11 at 06:49 PM

    Thank you for your time Don.

    I am with about the upgrade. but we are in the middle of an urgency!

    I modified the reports to ODBC and ADO for test.

    Fortunately, In both cases, the .rpt files open correctly in CR, means everything is set correctly I see the report and correct report values.

    BUT, they could not be opened in VB6 correctly.

    I get this error for ADO and almost the same for ODBC with less details (I don't have any username password on Access database)

    Logon failed.      Details: ADO error Code: 0x80040e21     Source:Microsoft OLE DB Service Components                         Description: Multi-step OLE DB operation generated errors.Check each OLE DB status value, if Available. No work was done.

    in VB6 I simply use CrystalActivexReportViewer to open the .rpt file, no connection set at all.

    Appreciate your help.

    Add comment
    10|10000 characters needed characters exceeded

  • Jan 11 at 06:49 PM

    I have fixed it using ODBC.

    Special thanks

    Add comment
    10|10000 characters needed characters exceeded

  • Jan 20 at 05:06 PM

    Hi Don,

    really appreciate your help.

    I have solved my problem with .dsn file. Thanks

    I have an issue left now!

    How could I have relative path for database?

    the .dsn works fine with explicit file path like

    DefaultDir=C:\reports

    DBQ=C:\reports\myDB.MDB

    But if user changes the \report folder, like "c:\myDir\reports" .rpt could not find the path.

    I need the .dsn file connect to the database on relative (current) directory .

    Appreciate.

    Add comment
    10|10000 characters needed characters exceeded

  • Jan 21 at 04:46 PM

    Try mapping the folder as a shared folder in Explorer.exe

    Add comment
    10|10000 characters needed characters exceeded

  • Jan 21 at 05:50 PM

    The problem is users need to have different folders.

    Working with one folder is not the solution here, I need to have a dynamic address.

    Add comment
    10|10000 characters needed characters exceeded