[AccessD] 203 vs. 2007

Hi Rocky,

Probably not much help, but I have found a whole host of pissy little VBA errors with moving from legacy Access datbases (MDE's in this case) to Access 2007.  Most annoying.

Try unticking all the references and re-applying them - it may help.

good luck and post back if you get a solution.

regards
Darryl



-----Original Message-----
From: accessd-bounces at databaseadvisors.com [mailto:accessd-bounces at databaseadvisors.com] On Behalf Of Rocky Smolin
Sent: Thursday, 23 July 2009 11:16 AM
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

______________________________________________________________________
This email and any attachments may contain privileged and confidential
information and are intended for the named addressee only. If you have
received this e-mail in error, please notify the sender and delete
this e-mail immediately. Any confidentiality, privilege or copyright
is not waived or lost because this e-mail has been sent to you in
error. It is your responsibility to check this e-mail and any
attachments for viruses.  No warranty is made that this material is
free from computer virus or any other defect or error.  Any
loss/damage incurred by using this material is not the sender's
responsibility.  The sender's entire liability will be limited to
resupplying the material.
______________________________________________________________________