[AccessD] ADO code stopped working

tlb/dll My eyeballs get fuzzy watching Superbowl commercials

However you are using ADOX, so you need one more additional reference
if it is 2.8 MDAC you need a reference to

The Access reference
Microsoft ActiveX Data Object 2.7 Recordsets Library
should point at
C:\Program Files\Common Files\System\ado\msador15.dll

Jennifer Gross wrote:

>Thanks for the suggestions.  I set the references like Marty suggested
>and am still getting the problem.  I am using the Getz Developers
>Handbook code for looping through parameters in a select query:
>
>    Dim cmd As ADODB.Command
>    Dim rst As ADODB.Recordset
>    Dim prm As ADODB.Parameter
>    Dim cat As ADOX.Catalog
>    Dim prc As ADOX.Procedure
>
>    Set cat = New ADOX.Catalog
>*   cat.ActiveConnection = CurrentProject.Connection
>*   Set prc = cat.Procedures("TheQuery")
>    Set cmd = prc.Command
>    For Each prm In cmd.Parameters
>        prm.Value = Eval(prm.Name)
>    Next prm
>    Set rst = cmd.Execute
>
>If I don't use the query with parameters, but instead base the recordset
>on the table, then it works fine:
>
>    Set rst = New ADODB.Recordset
>    Set rst.ActiveConnection = CurrentProject.Connection
>    rst.CursorType = adOpenForwardOnly
>    rst.LockType = adLockReadOnly
>    rst.Open "TheTable"
>
>I am getting the same results whether the code is in the existing FE or
>if I create a new db with the ADO code as Rocky suggested.
>
>Any thoughts?
>
>Jennifer
>
>-----Original Message-----
>From: accessd-bounces at databaseadvisors.com
>[mailto:accessd-bounces at databaseadvisors.com] On Behalf Of Rocky Smolin
>at Beach Access Software
>Sent: Sunday, February 04, 2007 4:55 PM
>To: 'Access Developers discussion and problem solving'
>Subject: Re: [AccessD] ADO code stopped working
>
>
>I would whip up a small app with some ado code to see if the problem is
>inside your app or outside of it.  Does your app compile?
>
>Rocky
> 
>
>-----Original Message-----
>From: accessd-bounces at databaseadvisors.com
>[mailto:accessd-bounces at databaseadvisors.com] On Behalf Of Jennifer
>Gross
>Sent: Sunday, February 04, 2007 2:05 PM
>To: AccessD List
>Subject: [AccessD] ADO code stopped working
>
>Hi Everyone,
>
>W2K SP4 / A2K SP3 / terminal server
>
>I have a database that has some DAO and some ADO code.  Recently all ADO
>stopped working.  DAO is still working fine.  Anytime code utilizing ADO
>runs it shuts down the database abruptly, leaving the LDB file.  We were
>also having problems with the Windows Management databases locking up
>and a reinstall of the latest MDAC took care of that problem, but did
>not solve the ADO problem.  ADO was working fine for end of year
>reporting.  There are no missing references.  After the MDAC reinstall I
>unchecked references, closed down, opened up and rechecked references.
>
>Any help would be greatly appreciated.
>
>Thank you,
>
>Jennifer Gross
>databasics
>2839 Shirley Drive
>Newbury Park, CA 91320-3068
>office:  (805) 480-1921
>fax:	   (805) 499-0467 
>
>
>--
>AccessD mailing list
>AccessD at databaseadvisors.com
>http://databaseadvisors.com/mailman/listinfo/accessd
>Website: http://www.databaseadvisors.com
>
>--
>No virus found in this incoming message.
>Checked by AVG Free Edition.
>Version: 7.5.432 / Virus Database: 268.17.24/668 - Release Date:
>2/4/2007 1:30 AM
> 
>
>  
>

-- 
Marty Connelly
Victoria, B.C.
Canada