[AccessD] 203 vs. 2007

Just a shot in the dark - try moving the 'MS Office 12.0 Access Database
Engine Object Library' reference up until it's just below 'OLE Automation'.
That's where it is in my A2007 reference list. I think it's the library that
replaces DAO. I wonder if the 'Property' needs qualification, like
'DAO.Property'.  I'll try some experiments tomorrow on A2007.

Doug Steele

On Wed, Jul 22, 2009 at 6:15 PM, Rocky Smolin <rockysmolin at bchacc.com>wrote:

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