[AccessD] 203 vs. 2007

Rocky,

  Reference problems like that are age old with Access/VBA and apply to
A2000 and up (A95 and A97 didn't seem to have as many problems with
references).

  And FWIW, it's simpler just to check any unchecked reference, close the DB
and Access, then re-open and uncheck the reference just checked.  It forces
VBA to check and refresh all the references.

JimD. 

-----Original Message-----
From: accessd-bounces at databaseadvisors.com
[mailto:accessd-bounces at databaseadvisors.com] On Behalf Of Rocky Smolin
Sent: Wednesday, July 22, 2009 11:13 PM
To: 'Access Developers discussion and problem solving'
Subject: Re: [AccessD] 203 vs. 2007

Steve:

Believe it or not, unchecking all the references and then rechecking them
did the trick.  Who knew?

Rocky
 

-----Original Message-----
From: accessd-bounces at databaseadvisors.com
[mailto:accessd-bounces at databaseadvisors.com] On Behalf Of Steve Schapel
Sent: Wednesday, July 22, 2009 7:19 PM
To: Access Developers discussion and problem solving
Subject: Re: [AccessD] 203 vs. 2007

Rocky,

MS Office 12.0 Access Database Engine Object Library is the Access 2007
replacement for DAO.

You can't have both.

However, your code with DAO should not break, as it should automatically
reference the ACE library.

So I don't know specifically what's wrong.  But the first thing I would try
is change to:
Dim prp as DAO.Property

Regards
Steve


--------------------------------------------------
From: "Rocky Smolin" <rockysmolin at bchacc.com>
Sent: Thursday, July 23, 2009 1:15 PM
To: "'Access Developers discussion and problem solving'" 
<accessd at databaseadvisors.com>
Subject: [AccessD] 203 vs. 2007

> Dear List:
>
> I have a legacy app that was developed in 2003.  The client wants an 
> accde so in Access 2007 I opened the 2003 mdb and save it in 2007 
> format as an accdb.  I then opened the accdb but it has compile errors 
> which don't make sense.  Specifically I get a type mismatch on the .Name
property.
>
> Dim db as DAO.Database
> Dim prp as Property
> Set db = CurrentDb
> For Each prp in db.Properties
>
> And here I use prp.Name - gives a type mismatch on compile.  Name does 
> not appear in the list of properties when I type prp.
>
> Same problem with dim fld as Field referencing fld.Name - type mismatch.
> When I type fld. Name does not appear in the property list.
>
> Reference problem maybe?
>
> In the reference list I've got
>
> Visual Basic for Applications
> MS Access 12.0 Obj lib
> OLE Automation
> MS CDO for Windows 2000 Lib
> MS Calendar Control 2007
> MS Word 12.0 Obj Lib
> MS VB for Apps Extensibility 5.3
> MS Office 12.0 Access Database Engine Object Library
>
> I can't reference DAO 3.6 - gets a 'conflicts with another library' 
> error
>
> Any clues?
>
> MTIA
>
> Rocky
 

--
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