none
mde and Access 2010

    Question

  • What worked fine for years: Our frontend development mdb is of Access database format 2000 (backend is SQL Server). Developing works fine under every version of Access. The deployment process consists of copying the mdb to an XP and office 2000 machine, cleaning and debugging it if necessary from stuff too new, and having Access 2000 write an .mde. This has to be repeated for every interface language. These .mdes start up on every version of Access (and customers have all versions of Access) >= 2000 and works with every SQL Server (Express) version >= 2000. Except on Access 2010. An mde starts up with IsNull is no valid function and such and will not run stable. mdb, accdb and accde work fine. We have DAO 3.6 checked in the Refs and Dim DAO.... objects expressively many times ... Is there a solution / workaround for this? Compiling on (many different) target machines is NO solution, so please don't come up with this. It's not only a huge deployment process, but is very unprofessional in the eyes of the customers.

     

    Thanks for your questions and answers.

    mupan

    • Moved by Sally Tang Friday, December 03, 2010 5:59 AM (From:Office 2010 Setup and Deployment)
    • Edited by mupan Monday, December 06, 2010 11:51 AM English language ... hope it's better now
    Wednesday, December 01, 2010 4:36 PM

All replies

  • Hello mupan,

    If I understand correctly, you're creating an mde in Access 2000 and are having trouble using it in Access 2010.  Unfortunately, I cannot promise that databases created in old, unsupported versions of Access will continue to work as desired in the most recent release.  Recompilation in more recent versions of Access may be the only solution to your problem.

    Having said that, let's take a close look at what's actually happening.  Please let us know the exact syntax of any errors you're seeing and also what references your database contains.  From there we may be able to make a more specific determination as to why the database is not working in 2010.

    Thanks,
    Nathan Ost
    Microsoft Online Community Support

     


    Please remember to click "Mark as Answer" on the post that helps you, and to click "Unmark as Answer" if a marked post does not actually answer your question. This can be beneficial to other community members reading the thread.
    Friday, December 03, 2010 5:28 PM
  • Hello Nathan, thank you for your answer and your readiness to help me so far.

    If I understand correctly, you're creating an mde in Access 2000 and are having trouble using it in Access 2010.  Unfortunately, I cannot promise that databases created in old, unsupported versions of Access will continue to work as desired in the most recent release.  Recompilation in more recent versions of Access may be the only solution to your problem.

    Yes, you understand correctly. I am aware that we are dealing with old technology no longer supported by Microsoft. However, I tried to explain why we stick to these old technologies: to keep our customers happy. It should be clear that Access projects often target rather small companies resp. freelancers, as our project does. So we aim to enable our customers to run older software on older computers, and our efforts to keep Office and SQL Server 2000 on our system requirements list were successful in the past. Edit: Another issue is that for a longer period customers will have machines with Office 2010 installed while others still have older versions of Office, they will have to differentiate which of our clients to install.

    Having said that, let's take a close look at what's actually happening.  Please let us know the exact syntax of any errors you're seeing and also what references your database contains.  From there we may be able to make a more specific determination as to why the database is not working in 2010.

    Here's the error list.

    Undefined function 'IsNull' in expression. (3085)
    several (2 to 4) times: Application-defined or object-defined error (35010)
    Method 'accHelp' of object '_SubForm' failed (35021)
    Undefined function 'Mid' in expression. (3085)
    [Microsoft][ODBC SQL Server Driver][SQL Server]Fehler beim Konvertieren einer Zeichenfolge in einen datetime-Wert. (241)
    -- My translation: Error converting a string to a datetime value.
    There is an invalid use of the . (dot) or ! operator or invalid parentheses. (-2147352571)

    Access does not freeze or stop working by error at any time. Since .mdb and newer file formats do not show these errors, I cannot really give any hints about the lines of code or query that could be inflicted because I cannot step in when the error occurs.

    Now here's the refs list:

    ?references(1).Name, references(1).FullPath, references(1).Guid
    VBA           C:\PROGRA~1\COMMON~1\MICROS~1\VBA\VBA7\VBE7.DLL         {000204EF-0000-0000-C000-000000000046}
    Access        C:\Program Files\Microsoft Office\Office14\MSACC.OLB    {4AFFC9A0-5F99-101B-AF4E-00AA003F0F07}
    DAO                                                                   {00025E01-0000-0000-C000-000000000046}
    Office        C:\Program Files\Common Files\Microsoft Shared\OFFICE14\MSO.DLL       {2DF8D04C-5BFA-101B-BDE5-00AA0044DE52}
    MSComctlLib   C:\Windows\system32\MSCOMCTL.OCX          {831FDD16-0C5C-11D2-A9FC-0000F8754DA1}
    MSComCtl2     C:\Windows\system32\MSCOMCT2.OCX          {86CF1D34-0C5F-11D2-A9FC-0000F8754DA1}
    MSForms       C:\Windows\system32\FM20.DLL              {0D452EE1-E08F-101A-852E-02608C4D0BB4}
    stdole        C:\Windows\system32\stdole2.tlb           {00020430-0000-0000-C000-000000000046}
    MSHTML        C:\Windows\System32\mshtml.tlb            {3050F1C5-98B5-11CF-BB82-00AA00BDCE0B}
    vbSendMail    C:\Program Files\<product>\vbSendMail.dll     {332B82D3-3ED6-11D4-B1B5-00105AA5CCFF}
    Word          C:\Program Files\Microsoft Office\Office14\MSWORD.OLB   {00020905-0000-0000-C000-000000000046}

    None of them is reported IsBroken = -1, but DAO will refuse to list it's full path, error message:

    ---------------------------
    Microsoft Visual Basic for Applications
    ---------------------------
    Run-time error '-2147319779 (8002801d)':

    Automation error
    Library not registered.
    ---------------------------
    OK   Help   
    ---------------------------


    I manually regsvr32'd dao360.dll in %commonprogramfiles%\Microsoft Shared\DAO\, which was reported to be successful, but with no effect on my issue here.

    I got another customer report today who successfully started our .mde on Office 2010, but on Windows XP. So it might be that there is a Windows 7 related issue with one library (DAO?), rather than an Office version related one.

    It does not make any difference if I query the refs in the Immediate window like above before having started the .mde or when started up (with erorrs). It's exactly the same picture when I query the .mdb refs before and after starting up (without errors). The list is the same. But if DAO is the candidate, it seems as if the necessary substitution by ADO or whatever happens without any hint for me to know is only successful in an .mdb, not in an .mde.

    If this is not enough information, just ask.

    Kind regards,

    mupan
    Monday, December 06, 2010 12:19 PM
  • Dear Nathan, I am not trying to urge you, I am just fond to know if someone is working on my last post and if I should wait for an answer. Thank you very much. Kind regards, mupan
    Friday, December 10, 2010 7:53 AM
  • Hello mupan,

    The Access errors you're seeing are consistent with a broken VBA reference, and the "Library not registered" error you receive certainly supports that as the cause of the problem.  What is not consistent, however, is that the MDB that this problematic MDE was created from would not have the same issue, as all indications are that the problem should be machine-specific.

    The run-time error -2147319779 is generally a machine-specific problem.  Likewise, I was not able to reproduce the issue on a Windows 7 machine with only Access 2010 installed with an MDE created in Access 2000.  Furthermore, you indicated that at least one user does not see this same behavior on a Windows XP machine.  How many machines, then, are actually experiencing this problem?

    If the answer to this question is one then we need to look at registry permissions on that machine.  One thing you can try is to run Access as an administrator so that it runs with elevated privileges.  In addition to this, when you reregistered DAO, did you do so from an elevated administrative command prompt?  If not, you may want to open the Command Prompt window using the Run as Administrator option and then try registering the file again.  If you still see the same behavior then it may be worthwhile to use a tool like Process Monitor to create a log of what's happening when the application fails.  I would expect that the resulting log would contain either an ACCESS DENIED error on the registry keys related to DAO, or you might see Access searching for, better apparently never being able to find, dao360.dll.

    Process Monitor can be downloaded for free from:
    http://technet.microsoft.com/en-us/sysinternals/bb896645.aspx

    Best Regards,
    Nathan Ost
    Microsoft Online Community Support

     


    Please remember to click "Mark as Answer" on the post that helps you, and to click "Unmark as Answer" if a marked post does not actually answer your question. This can be beneficial to other community members reading the thread.
    Tuesday, December 14, 2010 5:17 PM
  • Hello Nathan,

    The Access errors you're seeing are consistent with a broken VBA reference, and the "Library not registered" error you receive certainly supports that as the cause of the problem.  What is not consistent, however, is that the MDB that this problematic MDE was created from would not have the same issue, as all indications are that the problem should be machine-specific.

    The run-time error -2147319779 is generally a machine-specific problem.  Likewise, I was not able to reproduce the issue on a Windows 7 machine with only Access 2010 installed with an MDE created in Access 2000.  Furthermore, you indicated that at least one user does not see this same behavior on a Windows XP machine.  How many machines, then, are actually experiencing this problem?

    I don't know, because as long as we don't have a solution for this we deploy "hand-made" accde's. At least I can reproduce the problem on my 7-2010-machine, and I know of another client with the same configuration who is now fed with an accde.

    If the answer to this question is one then we need to look at registry permissions on that machine.  One thing you can try is to run Access as an administrator so that it runs with elevated privileges.  In addition to this, when you reregistered DAO, did you do so from an elevated administrative command prompt?  If not, you may want to open the Command Prompt window using the Run as Administrator option and then try registering the file again.  If you still see the same behavior then it may be worthwhile to use a tool like Process Monitor to create a log of what's happening when the application fails.  I would expect that the resulting log would contain either an ACCESS DENIED error on the registry keys related to DAO, or you might see Access searching for, better apparently never being able to find, dao360.dll.

    There is no difference if I run our product as Admin or not. I already checked the registry permissions for HKLM\Software\Classes\* and the file system rights for the DAO directory. But I am not sure about the correct rights. Is it worthy to follow this trace? .mdb and .mde are run under the same user account and show their different behaviour. And the process monitor logs I attached show that the dao dll is found but locked for some reason I don't understand yet. I applied the following filter: "dao" in path, msaccess.exe in process name. If you think I might have missed something by this filter, let me know, and I apply another one.

    Process Monitor can be downloaded for free from:
    http://technet.microsoft.com/en-us/sysinternals/bb896645.aspx

    Thank you. All Sysinternals are on my machine ...

    I was also thinking again about the difference Access makes. I checked which ftype is associated to .mdb or .mde:

    C:\dev>assoc .mde
    .mde=Access.MDEFile.14

    C:\dev>assoc .mdb
    .mdb=Access.MDBFile

    Checking the type in HKLM\Software\Classes\ shows that the .mde is just opened, the .mdb is opened and there is some DDE statement sent to. Could this be a trace? I also tried to associate .mde to Access.MDBFile but this was of course not successful because Office setup checks and in case it's "necessary" rewrites the configuration every time you launch an Office program. And there is no norereg flag for Access like with Word, as far as I know.

    During several startups of our product I performed to gain the Process Monitor information I saw a dialog "Searching for a referenced file: dao360.dll" for the first time, and only once so far, while the .mdb version was loaded by Access 2010. Strange enough.

    Tuesday, December 21, 2010 5:02 PM
  • dao_log_mdB.csv:

    "Time of Day","Process Name","PID","Operation","Path","Result","Detail"
    "5:49:10.7534999 PM","MSACCESS.EXE","3872","CreateFile","C:\Program Files\COMMON FILES\MICROSOFT SHARED\OFFICE14\ACEDAO.DLL","SUCCESS","Desired Access: Generic Read, Disposition: Open, Options: Synchronous IO Non-Alert, Non-Directory File, Random Access, Attributes: n/a, ShareMode: Read, Delete, AllocationSize: n/a, OpenResult: Opened"
    "5:49:10.7535649 PM","MSACCESS.EXE","3872","ReadFile","C:\Program Files\COMMON FILES\MICROSOFT SHARED\OFFICE14\ACEDAO.DLL","SUCCESS","Offset: 0, Length: 64, Priority: Normal"
    "5:49:10.7535957 PM","MSACCESS.EXE","3872","ReadFile","C:\Program Files\COMMON FILES\MICROSOFT SHARED\OFFICE14\ACEDAO.DLL","SUCCESS","Offset: 272, Length: 4"
    "5:49:10.7536071 PM","MSACCESS.EXE","3872","ReadFile","C:\Program Files\COMMON FILES\MICROSOFT SHARED\OFFICE14\ACEDAO.DLL","SUCCESS","Offset: 276, Length: 20"
    "5:49:10.7536180 PM","MSACCESS.EXE","3872","ReadFile","C:\Program Files\COMMON FILES\MICROSOFT SHARED\OFFICE14\ACEDAO.DLL","SUCCESS","Offset: 520, Length: 40"
    "5:49:10.7536294 PM","MSACCESS.EXE","3872","ReadFile","C:\Program Files\COMMON FILES\MICROSOFT SHARED\OFFICE14\ACEDAO.DLL","SUCCESS","Offset: 560, Length: 40"
    "5:49:10.7536396 PM","MSACCESS.EXE","3872","ReadFile","C:\Program Files\COMMON FILES\MICROSOFT SHARED\OFFICE14\ACEDAO.DLL","SUCCESS","Offset: 600, Length: 40"
    "5:49:10.7536493 PM","MSACCESS.EXE","3872","ReadFile","C:\Program Files\COMMON FILES\MICROSOFT SHARED\OFFICE14\ACEDAO.DLL","SUCCESS","Offset: 640, Length: 40"
    "5:49:10.7536619 PM","MSACCESS.EXE","3872","ReadFile","C:\Program Files\COMMON FILES\MICROSOFT SHARED\OFFICE14\ACEDAO.DLL","SUCCESS","Offset: 455,680, Length: 16"
    "5:49:10.7536761 PM","MSACCESS.EXE","3872","ReadFile","C:\Program Files\COMMON FILES\MICROSOFT SHARED\OFFICE14\ACEDAO.DLL","SUCCESS","Offset: 455,696, Length: 8"
    "5:49:10.7536875 PM","MSACCESS.EXE","3872","ReadFile","C:\Program Files\COMMON FILES\MICROSOFT SHARED\OFFICE14\ACEDAO.DLL","SUCCESS","Offset: 455,912, Length: 2"
    "5:49:10.7536967 PM","MSACCESS.EXE","3872","ReadFile","C:\Program Files\COMMON FILES\MICROSOFT SHARED\OFFICE14\ACEDAO.DLL","SUCCESS","Offset: 455,914, Length: 14"
    "5:49:10.7537092 PM","MSACCESS.EXE","3872","ReadFile","C:\Program Files\COMMON FILES\MICROSOFT SHARED\OFFICE14\ACEDAO.DLL","SUCCESS","Offset: 455,720, Length: 16"
    "5:49:10.7537240 PM","MSACCESS.EXE","3872","ReadFile","C:\Program Files\COMMON FILES\MICROSOFT SHARED\OFFICE14\ACEDAO.DLL","SUCCESS","Offset: 455,736, Length: 8"
    "5:49:10.7537366 PM","MSACCESS.EXE","3872","ReadFile","C:\Program Files\COMMON FILES\MICROSOFT SHARED\OFFICE14\ACEDAO.DLL","SUCCESS","Offset: 455,792, Length: 16"
    "5:49:10.7537457 PM","MSACCESS.EXE","3872","ReadFile","C:\Program Files\COMMON FILES\MICROSOFT SHARED\OFFICE14\ACEDAO.DLL","SUCCESS","Offset: 455,808, Length: 8"
    "5:49:10.7537565 PM","MSACCESS.EXE","3872","ReadFile","C:\Program Files\COMMON FILES\MICROSOFT SHARED\OFFICE14\ACEDAO.DLL","SUCCESS","Offset: 455,864, Length: 16"
    "5:49:10.7537657 PM","MSACCESS.EXE","3872","QueryStandardInformationFile","C:\Program Files\COMMON FILES\MICROSOFT SHARED\OFFICE14\ACEDAO.DLL","SUCCESS","AllocationSize: 548,864, EndOfFile: 548,792, NumberOfLinks: 1, DeletePending: False, Directory: False"
    "5:49:10.7537759 PM","MSACCESS.EXE","3872","CreateFileMapping","C:\Program Files\COMMON FILES\MICROSOFT SHARED\OFFICE14\ACEDAO.DLL","FILE LOCKED WITH ONLY READERS","SyncType: SyncTypeCreateSection, PageProtection: PAGE_READONLY"
    "5:49:10.7537834 PM","MSACCESS.EXE","3872","QueryStandardInformationFile","C:\Program Files\COMMON FILES\MICROSOFT SHARED\OFFICE14\ACEDAO.DLL","SUCCESS","AllocationSize: 548,864, EndOfFile: 548,792, NumberOfLinks: 1, DeletePending: False, Directory: False"
    "5:49:10.7537913 PM","MSACCESS.EXE","3872","FASTIO_RELEASE_FOR_SECTION_SYNCHRONIZATION","C:\Program Files\COMMON FILES\MICROSOFT SHARED\OFFICE14\ACEDAO.DLL","SUCCESS",""
    "5:49:10.7537993 PM","MSACCESS.EXE","3872","CreateFileMapping","C:\Program Files\COMMON FILES\MICROSOFT SHARED\OFFICE14\ACEDAO.DLL","SUCCESS","SyncType: SyncTypeOther"
    "5:49:10.7538056 PM","MSACCESS.EXE","3872","FASTIO_RELEASE_FOR_SECTION_SYNCHRONIZATION","C:\Program Files\COMMON FILES\MICROSOFT SHARED\OFFICE14\ACEDAO.DLL","SUCCESS",""
    "5:49:11.2600381 PM","MSACCESS.EXE","3872","QueryOpen","C:\Program Files\Microsoft Office\Office14\ACEDAO.DLL","FAST IO DISALLOWED",""
    "5:49:11.2601687 PM","MSACCESS.EXE","3872","CreateFile","C:\Program Files\Microsoft Office\Office14\ACEDAO.DLL","SUCCESS","Desired Access: Read Attributes, Disposition: Open, Options: Open Reparse Point, Attributes: n/a, ShareMode: Read, Write, Delete, AllocationSize: n/a, OpenResult: Opened"
    "5:49:11.2602286 PM","MSACCESS.EXE","3872","QueryBasicInformationFile","C:\Program Files\Microsoft Office\Office14\ACEDAO.DLL","SUCCESS","CreationTime: 2010-03-23 9:55:00 AM, LastAccessTime: 2010-09-27 9:59:19 AM, LastWriteTime: 2010-03-23 9:55:00 AM, ChangeTime: 2010-09-27 9:59:19 AM, FileAttributes: A"
    "5:49:11.2602383 PM","MSACCESS.EXE","3872","CloseFile","C:\Program Files\Microsoft Office\Office14\ACEDAO.DLL","SUCCESS",""
    "5:49:11.2602640 PM","MSACCESS.EXE","3872","IRP_MJ_CLOSE","C:\Program Files\Microsoft Office\Office14\ACEDAO.DLL","SUCCESS",""
    "5:49:11.2604105 PM","MSACCESS.EXE","3872","CreateFile","C:\Program Files\Microsoft Office\Office14\ACEDAO.DLL","SUCCESS","Desired Access: Read Data/List Directory, Execute/Traverse, Synchronize, Disposition: Open, Options: Synchronous IO Non-Alert, Non-Directory File, Attributes: n/a, ShareMode: Read, Delete, AllocationSize: n/a, OpenResult: Opened"
    "5:49:11.2604830 PM","MSACCESS.EXE","3872","CreateFileMapping","C:\Program Files\Microsoft Office\Office14\ACEDAO.DLL","FILE LOCKED WITH ONLY READERS","SyncType: SyncTypeCreateSection, PageProtection: PAGE_EXECUTE"
    "5:49:11.2605018 PM","MSACCESS.EXE","3872","FASTIO_ACQUIRE_FOR_CC_FLUSH","C:\Program Files\Microsoft Office\Office14\ACEDAO.DLL","SUCCESS",""
    "5:49:11.2605200 PM","MSACCESS.EXE","3872","FASTIO_RELEASE_FOR_CC_FLUSH","C:\Program Files\Microsoft Office\Office14\ACEDAO.DLL","SUCCESS",""
    "5:49:11.2605286 PM","MSACCESS.EXE","3872","FASTIO_RELEASE_FOR_SECTION_SYNCHRONIZATION","C:\Program Files\Microsoft Office\Office14\ACEDAO.DLL","SUCCESS",""
    "5:49:11.2609215 PM","MSACCESS.EXE","3872","CreateFileMapping","C:\Program Files\Microsoft Office\Office14\ACEDAO.DLL","SUCCESS","SyncType: SyncTypeOther"
    "5:49:11.2609295 PM","MSACCESS.EXE","3872","FASTIO_RELEASE_FOR_SECTION_SYNCHRONIZATION","C:\Program Files\Microsoft Office\Office14\ACEDAO.DLL","SUCCESS",""
    "5:49:11.2611884 PM","MSACCESS.EXE","3872","Load Image","C:\Program Files\Microsoft Office\Office14\ACEDAO.DLL","SUCCESS","Image Base: 0x58730000, Image Size: 0x88000"
    "5:49:11.2612187 PM","MSACCESS.EXE","3872","CloseFile","C:\Program Files\Microsoft Office\Office14\ACEDAO.DLL","SUCCESS",""
    "5:49:11.2612500 PM","MSACCESS.EXE","3872","IRP_MJ_CLOSE","C:\Program Files\Microsoft Office\Office14\ACEDAO.DLL","SUCCESS",""
    "5:49:11.2615415 PM","MSACCESS.EXE","3872","CreateFile","C:\Program Files\Microsoft Office\Office14\ACEDAO.DLL","SUCCESS","Desired Access: Generic Read, Disposition: Open, Options: Synchronous IO Non-Alert, Non-Directory File, Attributes: n/a, ShareMode: Read, Delete, AllocationSize: n/a, OpenResult: Opened"
    "5:49:11.2616065 PM","MSACCESS.EXE","3872","QueryBasicInformationFile","C:\Program Files\Microsoft Office\Office14\ACEDAO.DLL","SUCCESS","CreationTime: 2010-03-23 9:55:00 AM, LastAccessTime: 2010-09-27 9:59:19 AM, LastWriteTime: 2010-03-23 9:55:00 AM, ChangeTime: 2010-09-27 9:59:19 AM, FileAttributes: A"
    "5:49:11.2618985 PM","MSACCESS.EXE","3872","CloseFile","C:\Program Files\Microsoft Office\Office14\ACEDAO.DLL","SUCCESS",""
    "5:49:11.2619321 PM","MSACCESS.EXE","3872","IRP_MJ_CLOSE","C:\Program Files\Microsoft Office\Office14\ACEDAO.DLL","SUCCESS",""
    "5:49:11.2636915 PM","MSACCESS.EXE","3872","RegQueryValue","HKLM\SOFTWARE\Microsoft\Windows NT\CurrentVersion\Image File Execution Options\DllNXOptions\acedao.dll","NAME NOT FOUND","Length: 1,024"
    "5:51:54.4403876 PM","MSACCESS.EXE","3872","CloseFile","C:\Program Files\COMMON FILES\MICROSOFT SHARED\OFFICE14\ACEDAO.DLL","SUCCESS",""

    • Edited by mupan Tuesday, December 21, 2010 5:15 PM
    Tuesday, December 21, 2010 5:10 PM
  • dao_log_mdE.csv:

    "Time of Day","Process Name","PID","Operation","Path","Result","Detail"
    "5:38:09.3052140 PM","MSACCESS.EXE","4280","QueryOpen","C:\Program Files\Microsoft Office\Office14\ACEDAO.DLL","FAST IO DISALLOWED",""
    "5:38:09.3053429 PM","MSACCESS.EXE","4280","CreateFile","C:\Program Files\Microsoft Office\Office14\ACEDAO.DLL","SUCCESS","Desired Access: Read Attributes, Disposition: Open, Options: Open Reparse Point, Attributes: n/a, ShareMode: Read, Write, Delete, AllocationSize: n/a, OpenResult: Opened"
    "5:38:09.3054045 PM","MSACCESS.EXE","4280","QueryBasicInformationFile","C:\Program Files\Microsoft Office\Office14\ACEDAO.DLL","SUCCESS","CreationTime: 2010-03-23 9:55:00 AM, LastAccessTime: 2010-09-27 9:59:19 AM, LastWriteTime: 2010-03-23 9:55:00 AM, ChangeTime: 2010-09-27 9:59:19 AM, FileAttributes: A"
    "5:38:09.3054147 PM","MSACCESS.EXE","4280","CloseFile","C:\Program Files\Microsoft Office\Office14\ACEDAO.DLL","SUCCESS",""
    "5:38:09.3054398 PM","MSACCESS.EXE","4280","IRP_MJ_CLOSE","C:\Program Files\Microsoft Office\Office14\ACEDAO.DLL","SUCCESS",""
    "5:38:09.3055955 PM","MSACCESS.EXE","4280","CreateFile","C:\Program Files\Microsoft Office\Office14\ACEDAO.DLL","SUCCESS","Desired Access: Read Data/List Directory, Execute/Traverse, Synchronize, Disposition: Open, Options: Synchronous IO Non-Alert, Non-Directory File, Attributes: n/a, ShareMode: Read, Delete, AllocationSize: n/a, OpenResult: Opened"
    "5:38:09.3056560 PM","MSACCESS.EXE","4280","CreateFileMapping","C:\Program Files\Microsoft Office\Office14\ACEDAO.DLL","FILE LOCKED WITH ONLY READERS","SyncType: SyncTypeCreateSection, PageProtection: PAGE_EXECUTE"
    "5:38:09.3056748 PM","MSACCESS.EXE","4280","FASTIO_RELEASE_FOR_SECTION_SYNCHRONIZATION","C:\Program Files\Microsoft Office\Office14\ACEDAO.DLL","SUCCESS",""
    "5:38:09.3060803 PM","MSACCESS.EXE","4280","CreateFileMapping","C:\Program Files\Microsoft Office\Office14\ACEDAO.DLL","SUCCESS","SyncType: SyncTypeOther"
    "5:38:09.3060883 PM","MSACCESS.EXE","4280","FASTIO_RELEASE_FOR_SECTION_SYNCHRONIZATION","C:\Program Files\Microsoft Office\Office14\ACEDAO.DLL","SUCCESS",""
    "5:38:09.3064151 PM","MSACCESS.EXE","4280","Load Image","C:\Program Files\Microsoft Office\Office14\ACEDAO.DLL","SUCCESS","Image Base: 0x56540000, Image Size: 0x88000"
    "5:38:09.3064538 PM","MSACCESS.EXE","4280","CloseFile","C:\Program Files\Microsoft Office\Office14\ACEDAO.DLL","SUCCESS",""
    "5:38:09.3064972 PM","MSACCESS.EXE","4280","IRP_MJ_CLOSE","C:\Program Files\Microsoft Office\Office14\ACEDAO.DLL","SUCCESS",""
    "5:38:09.3068485 PM","MSACCESS.EXE","4280","CreateFile","C:\Program Files\Microsoft Office\Office14\ACEDAO.DLL","SUCCESS","Desired Access: Generic Read, Disposition: Open, Options: Synchronous IO Non-Alert, Non-Directory File, Attributes: n/a, ShareMode: Read, Delete, AllocationSize: n/a, OpenResult: Opened"
    "5:38:09.3069323 PM","MSACCESS.EXE","4280","QueryBasicInformationFile","C:\Program Files\Microsoft Office\Office14\ACEDAO.DLL","SUCCESS","CreationTime: 2010-03-23 9:55:00 AM, LastAccessTime: 2010-09-27 9:59:19 AM, LastWriteTime: 2010-03-23 9:55:00 AM, ChangeTime: 2010-09-27 9:59:19 AM, FileAttributes: A"
    "5:38:09.3070549 PM","MSACCESS.EXE","4280","CloseFile","C:\Program Files\Microsoft Office\Office14\ACEDAO.DLL","SUCCESS",""
    "5:38:09.3070840 PM","MSACCESS.EXE","4280","IRP_MJ_CLOSE","C:\Program Files\Microsoft Office\Office14\ACEDAO.DLL","SUCCESS",""
    "5:38:09.3087322 PM","MSACCESS.EXE","4280","RegQueryValue","HKLM\SOFTWARE\Microsoft\Windows NT\CurrentVersion\Image File Execution Options\DllNXOptions\acedao.dll","NAME NOT FOUND","Length: 1,024"
    "5:38:09.3675121 PM","MSACCESS.EXE","4280","CreateFile","C:\Program Files\COMMON FILES\MICROSOFT SHARED\OFFICE14\ACEDAO.DLL","SUCCESS","Desired Access: Generic Read, Disposition: Open, Options: Synchronous IO Non-Alert, Non-Directory File, Random Access, Attributes: n/a, ShareMode: Read, Delete, AllocationSize: n/a, OpenResult: Opened"
    "5:38:09.3675914 PM","MSACCESS.EXE","4280","ReadFile","C:\Program Files\COMMON FILES\MICROSOFT SHARED\OFFICE14\ACEDAO.DLL","SUCCESS","Offset: 0, Length: 64, Priority: Normal"
    "5:38:09.3676381 PM","MSACCESS.EXE","4280","ReadFile","C:\Program Files\COMMON FILES\MICROSOFT SHARED\OFFICE14\ACEDAO.DLL","SUCCESS","Offset: 272, Length: 4"
    "5:38:09.3676512 PM","MSACCESS.EXE","4280","ReadFile","C:\Program Files\COMMON FILES\MICROSOFT SHARED\OFFICE14\ACEDAO.DLL","SUCCESS","Offset: 276, Length: 20"
    "5:38:09.3676632 PM","MSACCESS.EXE","4280","ReadFile","C:\Program Files\COMMON FILES\MICROSOFT SHARED\OFFICE14\ACEDAO.DLL","SUCCESS","Offset: 520, Length: 40"
    "5:38:09.3676780 PM","MSACCESS.EXE","4280","ReadFile","C:\Program Files\COMMON FILES\MICROSOFT SHARED\OFFICE14\ACEDAO.DLL","SUCCESS","Offset: 560, Length: 40"
    "5:38:09.3676894 PM","MSACCESS.EXE","4280","ReadFile","C:\Program Files\COMMON FILES\MICROSOFT SHARED\OFFICE14\ACEDAO.DLL","SUCCESS","Offset: 600, Length: 40"
    "5:38:09.3677003 PM","MSACCESS.EXE","4280","ReadFile","C:\Program Files\COMMON FILES\MICROSOFT SHARED\OFFICE14\ACEDAO.DLL","SUCCESS","Offset: 640, Length: 40"
    "5:38:09.3677134 PM","MSACCESS.EXE","4280","ReadFile","C:\Program Files\COMMON FILES\MICROSOFT SHARED\OFFICE14\ACEDAO.DLL","SUCCESS","Offset: 455,680, Length: 16"
    "5:38:09.3677282 PM","MSACCESS.EXE","4280","ReadFile","C:\Program Files\COMMON FILES\MICROSOFT SHARED\OFFICE14\ACEDAO.DLL","SUCCESS","Offset: 455,696, Length: 8"
    "5:38:09.3677408 PM","MSACCESS.EXE","4280","ReadFile","C:\Program Files\COMMON FILES\MICROSOFT SHARED\OFFICE14\ACEDAO.DLL","SUCCESS","Offset: 455,912, Length: 2"
    "5:38:09.3677505 PM","MSACCESS.EXE","4280","ReadFile","C:\Program Files\COMMON FILES\MICROSOFT SHARED\OFFICE14\ACEDAO.DLL","SUCCESS","Offset: 455,914, Length: 14"
    "5:38:09.3677647 PM","MSACCESS.EXE","4280","ReadFile","C:\Program Files\COMMON FILES\MICROSOFT SHARED\OFFICE14\ACEDAO.DLL","SUCCESS","Offset: 455,720, Length: 16"
    "5:38:09.3677761 PM","MSACCESS.EXE","4280","ReadFile","C:\Program Files\COMMON FILES\MICROSOFT SHARED\OFFICE14\ACEDAO.DLL","SUCCESS","Offset: 455,736, Length: 8"
    "5:38:09.3677887 PM","MSACCESS.EXE","4280","ReadFile","C:\Program Files\COMMON FILES\MICROSOFT SHARED\OFFICE14\ACEDAO.DLL","SUCCESS","Offset: 455,792, Length: 16"
    "5:38:09.3677984 PM","MSACCESS.EXE","4280","ReadFile","C:\Program Files\COMMON FILES\MICROSOFT SHARED\OFFICE14\ACEDAO.DLL","SUCCESS","Offset: 455,808, Length: 8"
    "5:38:09.3678098 PM","MSACCESS.EXE","4280","ReadFile","C:\Program Files\COMMON FILES\MICROSOFT SHARED\OFFICE14\ACEDAO.DLL","SUCCESS","Offset: 455,864, Length: 16"
    "5:38:09.3678195 PM","MSACCESS.EXE","4280","QueryStandardInformationFile","C:\Program Files\COMMON FILES\MICROSOFT SHARED\OFFICE14\ACEDAO.DLL","SUCCESS","AllocationSize: 548,864, EndOfFile: 548,792, NumberOfLinks: 1, DeletePending: False, Directory: False"
    "5:38:09.3678332 PM","MSACCESS.EXE","4280","CreateFileMapping","C:\Program Files\COMMON FILES\MICROSOFT SHARED\OFFICE14\ACEDAO.DLL","FILE LOCKED WITH ONLY READERS","SyncType: SyncTypeCreateSection, PageProtection: PAGE_READONLY"
    "5:38:09.3678406 PM","MSACCESS.EXE","4280","QueryStandardInformationFile","C:\Program Files\COMMON FILES\MICROSOFT SHARED\OFFICE14\ACEDAO.DLL","SUCCESS","AllocationSize: 548,864, EndOfFile: 548,792, NumberOfLinks: 1, DeletePending: False, Directory: False"
    "5:38:09.3678497 PM","MSACCESS.EXE","4280","FASTIO_RELEASE_FOR_SECTION_SYNCHRONIZATION","C:\Program Files\COMMON FILES\MICROSOFT SHARED\OFFICE14\ACEDAO.DLL","SUCCESS",""
    "5:38:09.3678588 PM","MSACCESS.EXE","4280","CreateFileMapping","C:\Program Files\COMMON FILES\MICROSOFT SHARED\OFFICE14\ACEDAO.DLL","SUCCESS","SyncType: SyncTypeOther"
    "5:38:09.3678657 PM","MSACCESS.EXE","4280","FASTIO_RELEASE_FOR_SECTION_SYNCHRONIZATION","C:\Program Files\COMMON FILES\MICROSOFT SHARED\OFFICE14\ACEDAO.DLL","SUCCESS",""
    "5:38:09.3940596 PM","MSACCESS.EXE","4280","CreateFile","C:\Program Files\COMMON FILES\MICROSOFT SHARED\DAO\dao360.dll","SUCCESS","Desired Access: Generic Read, Disposition: Open, Options: Synchronous IO Non-Alert, Non-Directory File, Random Access, Attributes: n/a, ShareMode: Read, Delete, AllocationSize: n/a, OpenResult: Opened"
    "5:38:09.3943539 PM","MSACCESS.EXE","4280","ReadFile","C:\Program Files\COMMON FILES\MICROSOFT SHARED\DAO\dao360.dll","SUCCESS","Offset: 0, Length: 64, Priority: Normal"
    "5:38:09.3943950 PM","MSACCESS.EXE","4280","ReadFile","C:\Program Files\COMMON FILES\MICROSOFT SHARED\DAO\dao360.dll","SUCCESS","Offset: 232, Length: 4"
    "5:38:09.3944069 PM","MSACCESS.EXE","4280","ReadFile","C:\Program Files\COMMON FILES\MICROSOFT SHARED\DAO\dao360.dll","SUCCESS","Offset: 236, Length: 20"
    "5:38:09.3944229 PM","MSACCESS.EXE","4280","ReadFile","C:\Program Files\COMMON FILES\MICROSOFT SHARED\DAO\dao360.dll","SUCCESS","Offset: 480, Length: 40"
    "5:38:09.3944366 PM","MSACCESS.EXE","4280","ReadFile","C:\Program Files\COMMON FILES\MICROSOFT SHARED\DAO\dao360.dll","SUCCESS","Offset: 520, Length: 40"
    "5:38:09.3944492 PM","MSACCESS.EXE","4280","ReadFile","C:\Program Files\COMMON FILES\MICROSOFT SHARED\DAO\dao360.dll","SUCCESS","Offset: 560, Length: 40"
    "5:38:09.3944600 PM","MSACCESS.EXE","4280","ReadFile","C:\Program Files\COMMON FILES\MICROSOFT SHARED\DAO\dao360.dll","SUCCESS","Offset: 600, Length: 40"
    "5:38:09.3944708 PM","MSACCESS.EXE","4280","ReadFile","C:\Program Files\COMMON FILES\MICROSOFT SHARED\DAO\dao360.dll","SUCCESS","Offset: 640, Length: 40"
    "5:38:09.3944839 PM","MSACCESS.EXE","4280","ReadFile","C:\Program Files\COMMON FILES\MICROSOFT SHARED\DAO\dao360.dll","SUCCESS","Offset: 524,288, Length: 16"
    "5:38:09.3945028 PM","MSACCESS.EXE","4280","ReadFile","C:\Program Files\COMMON FILES\MICROSOFT SHARED\DAO\dao360.dll","SUCCESS","Offset: 524,304, Length: 8"
    "5:38:09.3945164 PM","MSACCESS.EXE","4280","ReadFile","C:\Program Files\COMMON FILES\MICROSOFT SHARED\DAO\dao360.dll","SUCCESS","Offset: 524,448, Length: 2"
    "5:38:09.3945261 PM","MSACCESS.EXE","4280","ReadFile","C:\Program Files\COMMON FILES\MICROSOFT SHARED\DAO\dao360.dll","SUCCESS","Offset: 524,450, Length: 14"
    "5:38:09.3945421 PM","MSACCESS.EXE","4280","ReadFile","C:\Program Files\COMMON FILES\MICROSOFT SHARED\DAO\dao360.dll","SUCCESS","Offset: 524,320, Length: 16"
    "5:38:09.3945598 PM","MSACCESS.EXE","4280","ReadFile","C:\Program Files\COMMON FILES\MICROSOFT SHARED\DAO\dao360.dll","SUCCESS","Offset: 524,336, Length: 8"
    "5:38:09.3945729 PM","MSACCESS.EXE","4280","ReadFile","C:\Program Files\COMMON FILES\MICROSOFT SHARED\DAO\dao360.dll","SUCCESS","Offset: 524,368, Length: 16"
    "5:38:09.3945826 PM","MSACCESS.EXE","4280","ReadFile","C:\Program Files\COMMON FILES\MICROSOFT SHARED\DAO\dao360.dll","SUCCESS","Offset: 524,384, Length: 8"
    "5:38:09.3945934 PM","MSACCESS.EXE","4280","ReadFile","C:\Program Files\COMMON FILES\MICROSOFT SHARED\DAO\dao360.dll","SUCCESS","Offset: 524,416, Length: 16"
    "5:38:09.3946037 PM","MSACCESS.EXE","4280","QueryStandardInformationFile","C:\Program Files\COMMON FILES\MICROSOFT SHARED\DAO\dao360.dll","SUCCESS","AllocationSize: 610,304, EndOfFile: 610,304, NumberOfLinks: 2, DeletePending: False, Directory: False"
    "5:38:09.3946168 PM","MSACCESS.EXE","4280","CreateFileMapping","C:\Program Files\COMMON FILES\MICROSOFT SHARED\DAO\dao360.dll","FILE LOCKED WITH ONLY READERS","SyncType: SyncTypeCreateSection, PageProtection: PAGE_READONLY"
    "5:38:09.3946265 PM","MSACCESS.EXE","4280","QueryStandardInformationFile","C:\Program Files\COMMON FILES\MICROSOFT SHARED\DAO\dao360.dll","SUCCESS","AllocationSize: 610,304, EndOfFile: 610,304, NumberOfLinks: 2, DeletePending: False, Directory: False"
    "5:38:09.3946351 PM","MSACCESS.EXE","4280","FASTIO_RELEASE_FOR_SECTION_SYNCHRONIZATION","C:\Program Files\COMMON FILES\MICROSOFT SHARED\DAO\dao360.dll","SUCCESS",""
    "5:38:09.3946465 PM","MSACCESS.EXE","4280","CreateFileMapping","C:\Program Files\Common Files\microsoft shared\DAO\dao360.dll","SUCCESS","SyncType: SyncTypeOther"
    "5:38:09.3946545 PM","MSACCESS.EXE","4280","FASTIO_RELEASE_FOR_SECTION_SYNCHRONIZATION","C:\Program Files\Common Files\microsoft shared\DAO\dao360.dll","SUCCESS",""
    "5:38:38.5289053 PM","MSACCESS.EXE","4280","CloseFile","C:\Program Files\COMMON FILES\MICROSOFT SHARED\OFFICE14\ACEDAO.DLL","SUCCESS",""
    "5:38:39.0417704 PM","MSACCESS.EXE","4280","CloseFile","C:\Program Files\COMMON FILES\MICROSOFT SHARED\DAO\dao360.dll","SUCCESS",""

    Tuesday, December 21, 2010 5:15 PM
  • Hello Mupan,

     

    I took a similar trace on my machine and saw that there are indeed different calls made to dao360.dll and ACEDAO.dll depending on whether an MDE or MDB file was being opened.  Unfortunately, this isn't necessarily problematic in and of itself.  The functionality of my sample database remained intact, so despite the difference in behavior, everything still works fine.

     

    There really isn't enough information to determine whether the problem may be something specific to your machine, or possibly something particular with your database that is causing the problem to occur.  Sending us a copy of the database would allow us to determine this.  Unfortunately, that is really beyond the scope of what I can help you with in a forum thread, though.

     

    That being said, I don't know that there is much more I can do to assist you in this context, but perhaps someone else on the forum may still have some suggestions.  If you would like us to do further investigation in to this issue, we will need you to go ahead and create a support case.  You can create one online at the following address:

    http://support.microsoft.com/default.aspx?id=fh;en-us;offerprophone

     

    Best Regards,

    Nathan Ost

    Microsoft Online Community Support


    Please remember to click "Mark as Answer" on the post that helps you, and to click "Unmark as Answer" if a marked post does not actually answer your question. This can be beneficial to other community members reading the thread.
    Tuesday, December 21, 2010 10:49 PM
  • Hella Nathan,

    Hello Mupan,

     

    I took a similar trace on my machine and saw that there are indeed different calls made to dao360.dll and ACEDAO.dll depending on whether an MDE or MDB file was being opened.  Unfortunately, this isn't necessarily problematic in and of itself.  The functionality of my sample database remained intact, so despite the difference in behavior, everything still works fine.

     

    I would not do anything else but trying to reproduce the error, and I understand that from your point of view this is not a failure of Access (2010) if you cannot reproduce it. But in this case that means you ignore some details I reported in my posts in this thread, that make clear that our mdb is properly programmed.

    There really isn't enough information to determine whether the problem may be something specific to your machine, or possibly something particular with your database that is causing the problem to occur.  Sending us a copy of the database would allow us to determine this.  Unfortunately, t hat is really beyond the scope of what I can help you with in a forum thread, though.

    No, it's rather no problem of the mdb/mde or my machine, because, as I told you, the errors occur exactly the same on another Windows 7 machine with an mde in Access 2010 while everything works fine on other machines and on the same Windows 7 and Office 2010 machines with an mdb.

    Additionally, I now encountered Office 2010 changing the DAO ref to a completely new reference with a new guid. I could not report that before because it will not appear immediately after loading an mdb in Access 2010, but at some later time working with the mdb and editing it in Access 2010. I know that behaviour from the Word library while with that library there is no upwards compatibility problem. DAO though has an upward compatibility issue. I would not be surprised if that was on purpose; M$ has learned in the past that their customers take everything.

    Since our database is a (closed source) product I am not entitled to send it to you.

     

    That being said, I don't know that there is much more I can do to assist you in this context, but perhaps someone else on the forum may still have some suggestions.  If you would like us to do further investigation in to this issue, we will need you to go ahead and create a support case.  You can create one online at the following address:

    http://support.microsoft.com/default.aspx?id=fh;en-us;offerprophone

     

    Best Regards,

    Nathan Ost

    Microsoft Online Community Support


    Please remember to click "Mark as Answer" on the post that helps you, and to click "Unmark as Answer" if a marked post does not actually answer your question. This can be beneficial to other community members reading the thread.

    I understand you cannot help me. It is no surprise that M$ community supporters are not informed about possible issues like that, so of course I don't blame you personally. But even if I was entitled to send the mdb or mde to you, I would not stand a bug report being treated as a support inquiry, and pay for it!, like I wasn't aware of what I'm doing. Yes, maybe someone else will be able to help me. I doubt it though.

    Best regards,

    mupan

    Tuesday, January 04, 2011 2:04 PM
  • After Office 14 back on Office 9:

    ?references(10).guid
    {4AC9E1DA-5BAD-4AC7-86E3-24F4CDCECA28} (DAO)
    ?references(11).guid
    {00020905-0000-0000-C000-000000000046} (Word)


    Selecting Word 9 and DAO 3.6 lib, again check guid:

    ?references(10).name
    DAO
    ?references(10).guid
    {00025E01-0000-0000-C000-000000000046}

    ?references(11).name
    Word
    ?references(11).guid
    {00020905-0000-0000-C000-000000000046}


    DAO (ACEDAO) 14 has another guid in Office, Word libs from 9 to 14 have the same, so upward compatibility for Word is no problem, but for DAO.
    Wednesday, January 12, 2011 12:47 PM
  • I have been searching for some help with a very similar problem.

    I have an Access 2003 MDB distributed as a digitally-signed MDE which is in use by hundreds of my customers who run it on a variety of PC configurations.

    Once of my test PCs runs Windows 7 Home Edition 64-Bit with Office 2003 (but not Access 2003) and Access 2010 Runtime (32-bit) installed.  According to Microsoft, 32-bit applications should run fine in the 64-bit environment. My application works for a while and then suddenly fails with many runtime errors which indicate something is seriously wrong with the VBA and/or DAO environment.  When it goes wrong, if I 'Repair' the installation, it starts working again then fails shortly thereafter.  The problem is intermittent but usually happens if I switch users and run the application from another user account.  By adding some testing code I found that even something as simple as MSGBOX DCOUNT("*","lclAnalyseColumn"), where lclAnalyseColumn is a local table, fails with a message telling me: 'can't find object lclAnalyseColumn' - but it definitely exists as a Table!

    My theory is that this is a problem with the DAO DLL module failing in the 64-bit Windows environment.

    If I convert the source code to Access 2007, I see that the DAO Reference is changed to refer to ACEDAO.DLL.  By compiling this into an ACCDE, and running it in the same environment, I don't see the errors occurring.  This is not a satisfactory solution for me as I want to be able to distribute a single MDE file which can be run under Access 2003, 2007 or 2010 on any supported Windows version.

    If anyone would like to try my application to see if they can reproduce the problem in a 64-bit environment, the installation program can be downloaded from www.epsilon.net.nz/alpacamanager_download.html.

    You can see what References are in use by the database by using the 'Reference/System Tables/References' menu option.

    Richard Williams

    Wednesday, February 02, 2011 2:19 AM
  • Thank you very much, Richard.

    Your post is no answer, and the program situation is different when Access 2010's failure of self-configuration occurs on your or my machines. And my problem is reproducible in the computers where the incriminated combination of Office and Windows version is given.

    While all this is true, your post is a step towards a solution because it confirms that Microsoft's product in this regard simply neglects the requirements of developers resp. of their customers, in that it neglects upwards compatibility and rather forces the change to newer technologies.

    I found that it's the combination of 7 and 14 that is crucial. So if one day we find out the new security placebo in Windows 7 that is responsible and it should turn out to be influenced by program or by a local admin, the next step will be to find out a way to influence it in Windows 7 Home, and preferably by a script.

    Regards,

    mupan

    • Edited by mupan Wednesday, February 02, 2011 8:02 AM Formatting
    Wednesday, February 02, 2011 7:56 AM