Re: query mdb on network into Word. Access.exe not on workstation

From: Alex Ivanov (consul_at_collegeclub.com)
Date: 11/24/04 

Date: Wed, 24 Nov 2004 13:21:04 -0800

Well I ran into this problem couple of times. If dao350 has not been
registerd, adodb provider for Jet did not know what to do. 

-- 
Please reply to NG only. This email is not monitored.
Alex.
"Alex Dybenko" <alex@PLEASE.cemi.NO.rssi.SPAM.ru> wrote in message 
news:e5mG03g0EHA.3408@tk2msftngp13.phx.gbl...
> Well, not sure that ADO uses DAO. ADO uses OLE DB provider for jet, and 
> does not require DAO. Access itself uses DAO anytime - this can be.
> For example VB program connects to jet DB via ADO without DAO installed
>
> -- 
> Alex Dybenko (MVP)
> http://Alex.Dybenko.com
> http://www.PointLtd.com
>
>
>
> "Alex Ivanov" <consul@collegeclub.com> wrote in message 
> news:OqJ1kKe0EHA.2688@TK2MSFTNGP09.phx.gbl...
>> Actually, ADO uses DAO internally while connecting to Jet databases. So 
>> in this case ADO is just an extra layer of indirection, and extra 
>> overhead, if you wish, though not very significant. You may test it 
>> yourself: try to delete dao350.dll (or dao360.dll) and your code will 
>> blow up.
>> Simply renaming the files may or may not work because if Windows 
>> discovers that you're renaming registered files, it will try to change 
>> the registry entries accordingly.
>>
>> -- 
>> Please reply to NG only. This email is not monitored.
>> Alex.
>>
>>
>> "R. Choate" <rchoatecpa@NoSpam.com> wrote in message 
>> news:u8mrVgY0EHA.3832@TK2MSFTNGP10.phx.gbl...
>>> It occurred to me last night after thinking about your reply that the 
>>> users really only need to have ADO, not DAO, and that they
>>> also need to have a certain directory path available on their hard drive 
>>> which I specify in my code to look for and to deposit text
>>> files in, if the text files are not present already in that folder. It 
>>> turned out that the new workstations did not have the
>>> directory "C:/WINNT/TEMP", which is a normal directory from the first 
>>> days of NT to the recent versions of XP Pro operating systems.
>>> My code first attempts to look in that folder for 3 text files, and if 
>>> they are not present, then my code creates them using
>>> recordsets from a mdb on the user's network. By simply adding the 
>>> "C:/WINNT/TEMP" folder, the problem was solved. The users already
>>> have ADO 2.8 because it was installed with the Office installation. DAO 
>>> was not an issue since I use ADO.
>>>
>>> Thanks for your ideas. They led my thinking in the right direction.
>>> -- 
>>> RMC,CPA
>>>
>>>
>>> "Alex Ivanov" <consul@collegeclub.com> wrote in message 
>>> news:%23PSitJR0EHA.3692@TK2MSFTNGP14.phx.gbl...
>>> If you only need to access the database from Word to populate some 
>>> fields
>>> you don't need Access installed. DAO 3.5 should be installed with 
>>> Windows
>>> anyway, though it is not always registered properly.
>>> If your database is created with Access 2000 or later, you will need to
>>> install MDAC that contains DAO 3.6. I believe the latest MDACs (2.7 and
>>> after) don't have DAO at all, but I may be wrong on this, check the
>>> Microsoft site for details.
>>>
>>>
>>> -- 
>>> Please reply to NG only. This email is not monitored.
>>> Alex.
>>>
>>>
>>> "R. Choate" <rchoatecpa@NoSpam.com> wrote in message
>>> news:%23ycDasP0EHA.3900@TK2MSFTNGP10.phx.gbl...
>>>> To be as specific as I can, the users don't have Access on their
>>>> workstations. They do have a runtime version I believe, that came
>>>> with some 3rd party app, but they don't have Access. The workstations 
>>>> have
>>>> the "Small Business Edition" of Office, which does not
>>>> include Access. I think the MDAC thing is worth looking into. These are
>>>> Office 2003 workstations and an Office 2K mdb. Please tell
>>>> me what I can look at here.
>>>>
>>>> Thanks !
>>>>
>>>> -- 
>>>> RMC,CPA
>>>>
>>>>
>>>> "Alex Ivanov" <consul@collegeclub.com> wrote in message
>>>> news:uhAanI3zEHA.2676@TK2MSFTNGP12.phx.gbl...
>>>> If I understood your problem correctly, you probably don't have correct
>>>> MDAC
>>>> installed on new workstations. You may also try to find and manually
>>>> register msado15.dll normally at "C:\Program Files\Common
>>>> Files\System\ado\msado15.dll" and dao350.dll or dao360.dll ("C:\Program
>>>> Files\Common Files\Microsoft Shared\DAO\")
>>>>
>>>> -- 
>>>> Please reply to NG only. This email is not monitored.
>>>> Alex.
>>>>
>>>>
>>>> "R. Choate" <rchoatecpa@NoSpam.com> wrote in message
>>>> news:%23Wx1rZnzEHA.3452@TK2MSFTNGP14.phx.gbl...
>>>>>I have created a Word template that is just loaded with macros and
>>>>>userforms. Users on the network have a menu button in Word, which
>>>>> opens a Userform in Word. The code behind the userform uses ADO to 
>>>>> first
>>>>> check for a number of existing text files on their local
>>>>> hard drive. If the text files don't exist, or if the user clicks on a
>>>>> "Refresh" button, then the code queries the Access db, which
>>>>> is present on a network drive and then creates the needed text files 
>>>>> with
>>>>> the data.
>>>>>
>>>>> That was all fine and dandy until they started buying new workstations
>>>>> which don't have Access. They have the "Small Business
>>>>> Edition" of Office. Now, they can't connect to the db and perform the 
>>>>> ADO
>>>>> query against it. What can I do to make these work without
>>>>> everybody having to get a full-blown version of Office on each PC?
>>>>> -- 
>>>>> RMC,CPA
>>>>>
>>>>>
>>>>>
>>>>
>>>>
>>>>
>>>
>>>
>>>
>>
>>
>
>