Converting Access 2000 database to Access 2007

[Luka]

Hello,
I converted Access2000 database to Access2007. And it does not work properly
at all.
There are windows XP and, Ms office2007 loaded on my computer.
The directory with Database is Trusted.
Activated is option "Show message bar in all applications where content has
been blocked".
Activated is option “Enable all macrosâ€
Activated is Show all actions in macro Design.

First I cannot get rid of yellow triangles (with exclamation) in the
beginning of macro rows for some actions like: Echo, SetValue, Close……
SetValue row (with yellow triangle) is not executed.
The row with Condition (IsNull()) also has triangle. It does not execute
right. It returns False for Empty field.
Macros and codes run with no Action Failed window or Error message, to the
end.
Rewriting condition to a new row in this macro, triangle appears
immediately. And it does not work again.
Rewriting condition row in NEW macro, it works OK.

VBA references set from Access2000: (Everything is working there OK)
-Visual Basic For Application
-Microsoft Access 9.0 Object Library
-OLE Automation
-Microsoft DAO 3.6 Object Library
-Microsoft Excel 9.0 Object Library
-Microsoft OLE DB Error Library
-Microsoft ActiveX Data Object 2.5 Library

I read on:
http://www.accessmvp.com/TWickerath/articles/adodao.htm
that Access 2007 uses DAO libraries.
In a table with the “References appropriate to your version of Accessâ€
is default location for Access Object Library:
C:\Program Files\Microsoft Office\Office12\msacc.olb
But I cannot place it to Reference window.
Compailing database executes OK with no massage anything is wrong.
I am not VB expert, but I assume wrong execution is result of missing some
library in VBA references.
Is there any basic set of references that make Access2007 working OK.

Can you help me?

 

[Risse]

Hello,
I converted Access2000 database to Access2007. And it does not work
properly
at all.
There are windows XP and, Ms office2007 loaded on my computer.
The directory with Database is Trusted.
Activated is option "Show message bar in all applications where content
has
been blocked".
Activated is option "Enable all macros"
Activated is Show all actions in macro Design.

First I cannot get rid of yellow triangles (with exclamation) in the
beginning of macro rows for some actions like: Echo, SetValue, Close..
SetValue row (with yellow triangle) is not executed.
The row with Condition (IsNull()) also has triangle. It does not execute
right. It returns False for Empty field.
Macros and codes run with no Action Failed window or Error message, to the
end.
Rewriting condition to a new row in this macro, triangle appears
immediately. And it does not work again.
Rewriting condition row in NEW macro, it works OK.

VBA references set from Access2000: (Everything is working there OK)
-Visual Basic For Application
-Microsoft Access 9.0 Object Library
-OLE Automation
-Microsoft DAO 3.6 Object Library
-Microsoft Excel 9.0 Object Library
-Microsoft OLE DB Error Library
-Microsoft ActiveX Data Object 2.5 Library

I read on:
http://www.accessmvp.com/TWickerath/articles/adodao.htm
that Access 2007 uses DAO libraries.
In a table with the "References appropriate to your version of Access"
is default location for Access Object Library:
C:\Program Files\Microsoft Office\Office12\msacc.olb
But I cannot place it to Reference window.
Compailing database executes OK with no massage anything is wrong.
I am not VB expert, but I assume wrong execution is result of missing some
library in VBA references.
Is there any basic set of references that make Access2007 working OK.

Can you help me?

 

[roccogrand]

Luka,

I am not a VB expert but try these actions (I am assuming that you are
running all Office 2007 programs):

Backup your database.
Turn off all the references.
Close Access.
Restart the database.
Now turn the most recent references on. I suspect that you will be using
Excel 12, Access 12, etc. (I really don't understand all this stuff but I
try.)

To my knowledge you are correct, Access 2007 has DAO as the native
environment. Some actions do not work they way they did in Access 2000.
Check out Allen Browne's website for a complete rundown. And you may need to
purchase a couple Access VBA 2007 or 2010 (if you plan to upgrade next month)
books.

HTH

David