[AccessD] Office 2010

[Darryl Collins]

Yep, and to add to Stuart's comments.  It compiles now because it can.  With the missing reference still in place it will bug out, as Stuart explained, when it checks what references are requested vs what is available.

Hope that helps a bit.
Cheers
Darryl

-----Original Message-----
From: AccessD [mailto:accessd-bounces at databaseadvisors.com] On Behalf Of Stuart McLachlan
Sent: Friday, 6 November 2015 8:50 AM
To: Access Developers discussion and problem solving
Subject: Re: [AccessD] Office 2010

If you have a missing reference, like to an OCX, the error can crop up anywhere when Access is trying to re-compile itself.  The first time it comes across a a reference to any library during compilation, Access will chack that all of the required ones are available.

The "Set Myds = MyDb.OpenRecordset("  was not a  line of code containing an error.

It was just the first point  where Access went looking for libraries and found one missing. 

--
Stuart

On 5 Nov 2015 at 20:43, Kaup, Chester wrote:

> The problem is fixed but not in a way I expected. The old version of 
> the database was using the calendar control (MSCAL.OCX). I checked the 
> references and it was checked and of course stated MISSING. I 
> unchecked it and all the code compiles now. Why I do not know.
> 
> Thanks for the help.
> 
> -----Original Message-----
> From: AccessD [mailto:accessd-bounces at databaseadvisors.com] On Behalf 
> Of Rocky Smolin Sent: Thursday, November 05, 2015 2:23 PM To: 'Access 
> Developers discussion and problem solving' Subject: Re: [AccessD] 
> Office 2010
> 
> Stop the code.  On the VBA page go to Tools-->References.  One (or
> more) should be marked MISSING.  Scan down the list, find it and check 
> it.
> 
> I'm guessing you also have a reference to a VBA library from a version 
> of access later than the one you're using.  Make sure that one's 
> unchecked. Close the references dialog box and try a compile.  If 
> you've still got a problem it'll tell you.
> 
> Then write back and we'll make up some other solution. :)
> 
> HTH
> 
> Rocky
> 
> 
> -----Original Message-----
> From: AccessD [mailto:accessd-bounces at databaseadvisors.com] On Behalf 
> Of Kaup, Chester Sent: Thursday, November 05, 2015 12:18 PM To: Access 
> Developers discussion and problem solving Subject: Re: [AccessD] 
> Office 2010
> 
> I did the search and replace adding DAO to the Dim statement for 
> Database and Recordset.
> 
> The dbOpenTable in the following line generates the message "Compile 
> Error Cannot find project library". I am not expert enough to know how 
> to fix this. Your assistance appreciated.
> 
> Set Myds = MyDb.OpenRecordset("tbl One Manifold Production for a Time 
> Period", dbOpenTable)
> 
> 
> -----Original Message-----
> From: AccessD [mailto:accessd-bounces at databaseadvisors.com] On Behalf 
> Of John Colby Sent: Wednesday, November 04, 2015 6:14 PM To: Access 
> Developers discussion and problem solving Subject: Re: [AccessD] 
> Office 2010
> 
> It used to be that if you had ADO and DAO both referenced in the check 
> box list, then the ORDER of the listing mattered, and DAO should come 
> first. Basically ADO and DAO used the same names for some objects.
> 
> It is good habit to always use the prefix anyway, whether forced to or 
> not.
> 
> On 11/4/2015 3:27 PM, Kaup, Chester wrote:
> > My office computer recently got upgraded from Office 2007 to Office 
> > 2010.
> In my database in the code module I have Dim mydb as DAO database.
> Office 2010 seems to want me to put DAO in front of every recordset 
> dim statement. EX Dim RS1 as DAO.Recordset. Is there a better way than 
> having to do this for the entire database? > > Also since the calendar 
> control no longer exists what is a good solution? > > Thank you for 
> your thoughts.
> 
> --
> John W. Colby
> 
> --
> AccessD mailing list
> AccessD at databaseadvisors.com
> http://databaseadvisors.com/mailman/listinfo/accessd
> Website: http://www.databaseadvisors.com
> 
> --
> AccessD mailing list
> AccessD at databaseadvisors.com
> http://databaseadvisors.com/mailman/listinfo/accessd
> Website: http://www.databaseadvisors.com
> 
> 
> ---
> This email has been checked for viruses by Avast antivirus software.
> https://www.avast.com/antivirus
> 
> --
> AccessD mailing list
> AccessD at databaseadvisors.com
> http://databaseadvisors.com/mailman/listinfo/accessd
> Website: http://www.databaseadvisors.com
> 
> --
> AccessD mailing list
> AccessD at databaseadvisors.com
> http://databaseadvisors.com/mailman/listinfo/accessd
> Website: http://www.databaseadvisors.com
> 


-- 
AccessD mailing list
AccessD at databaseadvisors.com
http://databaseadvisors.com/mailman/listinfo/accessd
Website: http://www.databaseadvisors.com