Quick 2007 Upgrade Question
am 09.01.2008 15:35:41 von dan.allen.dc
I am looking for a quick sanity check, to make sure I my view of a
problem is reasonable.
Our organization just upgraded from Access 2003 to Access 2007. One
of our MS Access databases is not working the way it used to. It is
my understanding that this is a typical upgrade problem with Access
2007.
The database in question has a number of complex forms that talk to
one another. There is a lot of VBA code in the background making it
all work together.
After the upgrade to Access 2007, some of the screens stopped sending
information to one another.
Online, I found this statement regarding Access 2007:
Compatibility issues Access 2007 cannot understand some expressions
that work in previous versions. For example, this expression in the
Control Source of a text box results in #Name:
=[Form].[RecordsetClone].[RecordCount]
Soooooo.... is it reasonable for me to assume the problem is caused by
the type of compatibility issue noted above?
Someone who works with Acess all the time maybe sees this all the
time.
As always, any comments will be much appreciated.
Dan Allen
Re: Quick 2007 Upgrade Question
am 09.01.2008 15:59:13 von Jebusville
wrote in message
news:07352bfe-3c79-4ffa-8f33-9eba9da59e32@u10g2000prn.google groups.com...
>I am looking for a quick sanity check, to make sure I my view of a
> problem is reasonable.
>
> Our organization just upgraded from Access 2003 to Access 2007. One
> of our MS Access databases is not working the way it used to. It is
> my understanding that this is a typical upgrade problem with Access
> 2007.
>
> The database in question has a number of complex forms that talk to
> one another. There is a lot of VBA code in the background making it
> all work together.
>
> After the upgrade to Access 2007, some of the screens stopped sending
> information to one another.
>
> Online, I found this statement regarding Access 2007:
>
> Compatibility issues Access 2007 cannot understand some expressions
> that work in previous versions. For example, this expression in the
> Control Source of a text box results in #Name:
> =[Form].[RecordsetClone].[RecordCount]
>
> Soooooo.... is it reasonable for me to assume the problem is caused by
> the type of compatibility issue noted above?
>
> Someone who works with Acess all the time maybe sees this all the
> time.
>
> As always, any comments will be much appreciated.
>
> Dan Allen
>
>
I don't have A2007 yet but this might help you find out where to start
looking:
http://allenbrowne.com/Access2007.html
Keith.
www.keithwilby.com