[AccessD] 203 vs. 2007

Rocky,

Property exists in both DAO and ADO.  You need to disambiguate all
references to objects that exist in both models, i.e., DAO.Property.

Charlotte Foust 

-----Original Message-----
From: accessd-bounces at databaseadvisors.com
[mailto:accessd-bounces at databaseadvisors.com] On Behalf Of Rocky Smolin
Sent: Wednesday, July 22, 2009 6:16 PM
To: 'Access Developers discussion and problem solving'
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