Prev: Query linked to Excel doesn't work why cant i email things i dont understand
Next: In Windows 7...desktop icon...*My Computer*????
From: Sergio Torres on 29 Mar 2010 03:03 David, I ran the sysinternals process monitor and got the following when I click the checkbox selector inside the linked tables manager: Access tries to "QueryOpen" dao360.dll in several locations: C:\Program Files (x86)\Microsoft Office\Office12\dao360.dll C:\Users\Sergio\Documents\dao360.dll C:\Windows\SysWOW64\dao360.dll C:\Windows\system\dao360.dll C:\Windows\dao360.dll C:\Program Files (x86)\Microsoft Office\Office12\dao360.dll C:\Windows\SysWOW64\dao360.dll C:\Windows\dao360.dll C:\Windows\SysWOW64\wbem\dao360.dll C:\Windows\SysWOW64\WindowsPowerShell\v1.0\dao360.dll C:\Program Files (x86)\ATI Technologies\ATI.ACE\Core-Static\dao360.dll C:\Users\Sergio\Documents\dao360.dll and allways gets the result "FAST IO IS DISABLED". After each "QueryOpen" it tries to "CreateFile" dao360.dll in the same locations and always gets the result "Name Not Found". The only location in my PC where dao360.dll exists is C:\Program Files (x86)\Common Files\microsoft shared\DAO The other entry that stands out is it tries to CreateFile C:\Program Files (x86)\Microsoft Office\Office12\MSACC.OLB and treats it as a folder: tries to CreateFile C:\Program Files (x86)\Microsoft Office\Office12\MSACC.OLB\0 and others with the same path. The file C:\Program Files (x86)\Microsoft Office\Office12\MSACC.OLB exists, but it's a file not a folder. The result is always Name Invalis, Path Not Found and Access Denied. It seems to me this shows some error,but I am not clear of the exact implications. Does this meake sense to you? Thanks -- Sergio Torres C. (505) 897 2041 ___________________ http://www.stcsys.com ___________________ "David W. Fenton" wrote: > =?Utf-8?B?U2VyZ2lvIFRvcnJlcw==?= > <SergioTorres(a)discussions.microsoft.com> wrote in > news:AD37A3EB-3841-4E9F-8193-8B3AFF1DEFB0(a)microsoft.com: > > > What else can we try? > > I don't know! The DLL error makes it seem like there's something > wrong with your Access installation. > > One thing to try is to get the SysInternals Process Monitor and > filtering its results for every RESULT that's not SUCCESS. That > might turn up a missing component. > > http://technet.microsoft.com/en-us/sysinternals/bb896645.aspx > > You would then want to check the same thing (for the DLL that turns > up not being found) on a machine where the linked-table manager > works. > > I'm basicaly out of ideas at this point, though. All I can think of > is that your machine's NTFS permissions are set to something other > than the default permissions. > > -- > David W. Fenton http://www.dfenton.com/ > usenet at dfenton dot com http://www.dfenton.com/DFA/ > . >
From: David W. Fenton on 29 Mar 2010 13:34 =?Utf-8?B?U2VyZ2lvIFRvcnJlcw==?= <SergioTorres(a)discussions.microsoft.com> wrote in news:CED18DA3-E3C9-4300-9DA9-0147091AA4B7(a)microsoft.com: > It seems to me this shows some error,but I am not clear of the > exact implications. Does this meake sense to you? I'm in the same boat as you, i.e., it's obviously showing an error, but I have no idea what it all means! It looks to me like something to do with 32-bit support and virtualized directories. Other than that, I can't say. Certainly the fact that it never succeeds in finding DAO would be a pretty good indication of why it can't work! -- David W. Fenton http://www.dfenton.com/ usenet at dfenton dot com http://www.dfenton.com/DFA/
From: Tony Toews [MVP] on 29 Mar 2010 18:19 Sergio Torres <SergioTorres(a)discussions.microsoft.com> wrote: >I ran the sysinternals process monitor and got the following when I click >the checkbox selector inside the linked tables manager: > >Access tries to "QueryOpen" dao360.dll in several locations: > > C:\Program Files (x86)\Microsoft Office\Office12\dao360.dll > C:\Users\Sergio\Documents\dao360.dll > C:\Windows\SysWOW64\dao360.dll > C:\Windows\system\dao360.dll > C:\Windows\dao360.dll > C:\Program Files (x86)\Microsoft Office\Office12\dao360.dll > C:\Windows\SysWOW64\dao360.dll > C:\Windows\dao360.dll > C:\Windows\SysWOW64\wbem\dao360.dll > C:\Windows\SysWOW64\WindowsPowerShell\v1.0\dao360.dll > C:\Program Files (x86)\ATI Technologies\ATI.ACE\Core-Static\dao360.dll > C:\Users\Sergio\Documents\dao360.dll Very interesting. Has anyone suggest registering the dao dll in this thread yet? For example regsvr32 "C:\Program Files >(x86)\Common Files\microsoft shared\DAO". An easy way to register a file is to search for both files at one time (<insert name of your file> REGSVR32.EXE) then drag and drop the OCX/DLL onto the EXE. As most relevant DLLs and OCXs reside in c:\<your windows version>\system32 you can try in this directory first to minimize searching time. If that doesn't find both then go up a directory level to c:\<your windows version>. Tony -- Tony Toews, Microsoft Access MVP Tony's Main MS Access pages - http://www.granite.ab.ca/accsmstr.htm Tony's Microsoft Access Blog - http://msmvps.com/blogs/access/ For a convenient utility to keep your users FEs and other files updated see http://www.autofeupdater.com/ Granite Fleet Manager http://www.granitefleet.com/
From: Jonas Götte on 30 Mar 2010 06:49 stupidddddddddddddddddddddddddddddddddddddddddddd "David W. Fenton" <XXXusenet(a)dfenton.com.invalid> schrieb im Newsbeitrag news:Xns9D49A0476BC2Af99a49ed1d0c49c5bbb2(a)74.209.136.91... > =?Utf-8?B?U2VyZ2lvIFRvcnJlcw==?= > <SergioTorres(a)discussions.microsoft.com> wrote in > news:AD37A3EB-3841-4E9F-8193-8B3AFF1DEFB0(a)microsoft.com: > >> What else can we try? > > I don't know! The DLL error makes it seem like there's something > wrong with your Access installation. > > One thing to try is to get the SysInternals Process Monitor and > filtering its results for every RESULT that's not SUCCESS. That > might turn up a missing component. > > http://technet.microsoft.com/en-us/sysinternals/bb896645.aspx > > You would then want to check the same thing (for the DLL that turns > up not being found) on a machine where the linked-table manager > works. > > I'm basicaly out of ideas at this point, though. All I can think of > is that your machine's NTFS permissions are set to something other > than the default permissions. > > -- > David W. Fenton http://www.dfenton.com/ > usenet at dfenton dot com http://www.dfenton.com/DFA/
From: David W. Fenton on 30 Mar 2010 15:25
"Tony Toews [MVP]" <ttoews(a)telusplanet.net> wrote in news:6n92r5dbgkl73fkn3m1mg6jihst5vnhjb1(a)4ax.com: > Has anyone suggest registering the dao dll in this > thread yet? For example regsvr32 "C:\Program Files >>(x86)\Common Files\microsoft shared\DAO". > > An easy way to register a file is to search for both files at one > time (<insert name of your file> REGSVR32.EXE) then drag and drop > the OCX/DLL onto the EXE. As most relevant DLLs and OCXs reside > in c:\<your windows version>\system32 you can try in this > directory first to minimize searching time. If that doesn't find > both then go up a directory level to c:\<your windows version>. Well, on Vista/Win7, you have to run Regsvr32 as admin in order for it to work (unless you've turned off UAC and are running as admin), so you might be able to do what you suggest with drag and drop if you create a shortcut to Regsvr32 and set it to run as admin. There's also a 64-bit/32-bit issue here, and I dont' know if that's part of the problem or not. -- David W. Fenton http://www.dfenton.com/ usenet at dfenton dot com http://www.dfenton.com/DFA/ |