Access 14.0 Object Library Reference problem

[cw via AccessMonster.com]

I'm testing my 2007 applications with the new Beta version of Access 2010 and
having issues with the Front-End Client-side of the database.

- I opened up the Front end on my developer station using Access 2010
- I updated various forms & VBA code and saved the database out to the
network
- I then opened the database on a client machine using Access 2007 and get
Reference errors
- When I check Tools/References on the client, it shows the following:
- Missing Access 14.0 Object Library Reference & Missing Outlook 14.0 Object
Library Reference

Of course I know that this is due to Access 2007 using v12.0 & Access 2010 is
v14.0

Question: How do developers deal with this issue where the end-user may have
two different versions of Access (2007 & 2010)? Can I force Access 2010 (on
my developer system) to include the v12.0 references along with v 14.0?

Thanks,cw

 

[Douglas J. Steele]

I believe you need to have the user open Access "As Administrator".

 

[David C. Holley]

I'm testing my 2007 applications with the new Beta version of Access 2010
and
having issues with the Front-End Client-side of the database.

- I opened up the Front end on my developer station using Access 2010
- I updated various forms & VBA code and saved the database out to the
network
- I then opened the database on a client machine using Access 2007 and get
Reference errors
- When I check Tools/References on the client, it shows the following:
- Missing Access 14.0 Object Library Reference & Missing Outlook 14.0
Object
Library Reference

Of course I know that this is due to Access 2007 using v12.0 & Access 2010
is
v14.0

Question: How do developers deal with this issue where the end-user may
have
two different versions of Access (2007 & 2010)? Can I force Access 2010
(on
my developer system) to include the v12.0 references along with v 14.0?

The challenge is to ensure that your clients or your organization
understands that everyone needs to be on the same version across the board.
Obviously, if you develop an app in 2007 and some of the users have 2003,
there may be functionality that doesn't work. Personally, I would limit my
development with a beta to those apps that are most likely to be ready about
the same time as the full version is released.

 

[Alex Dybenko]

Hi,
I recommend to develop application using exact Access version as end-user
running, or at least lowest version, if they run multiple versions. No
problem (well, almost no) to run multiple access versions on same PC

--
Best regards,
___________
Alex Dybenko (MVP)
http://accessblog.net
http://www.PointLtd.com

 

[cw via AccessMonster.com]

Thanks for all the input..
Our company is set to migrate all users to Office 2010 next year when it
releases so I always like to have as much time as possible to migrate my
older Office apps. Currently, I have only one client user that is actually
"beta testing" my new 2010 front-end using 2007, (other than myself).

Regarding my testing of Access 2010, everything from my 2007 versions work
fine except the following:
- Had to migrate all Snapshot reports to PDF (finally have to say goodbye to
"ConvertReportToPDF" (Thanks again to Stephen Lebans!)
- Access 2010 adds the v14.0 references.

Can the v14.0 references be copied to the destination client?

I will also try running as Administrator..

Thanks,
cw

Hi,
I recommend to develop application using exact Access version as end-user
running, or at least lowest version, if they run multiple versions. No
problem (well, almost no) to run multiple access versions on same PC

I'm testing my 2007 applications with the new Beta version of Access 2010
and

[quoted text clipped - 21 lines]

Thanks,cw

 

[Douglas J. Steele]

If you're asking whether you can copy the v14 references to machines where
Office 2010 has not been installed, the answer is no.

--
Doug Steele, Microsoft Access MVP

(no e-mails, please!)

Thanks for all the input..
Our company is set to migrate all users to Office 2010 next year when it
releases so I always like to have as much time as possible to migrate my
older Office apps. Currently, I have only one client user that is actually
"beta testing" my new 2010 front-end using 2007, (other than myself).

Regarding my testing of Access 2010, everything from my 2007 versions work
fine except the following:
- Had to migrate all Snapshot reports to PDF (finally have to say goodbye
to
"ConvertReportToPDF" (Thanks again to Stephen Lebans!)
- Access 2010 adds the v14.0 references.

Can the v14.0 references be copied to the destination client?

I will also try running as Administrator..

Thanks,
cw

Hi,
I recommend to develop application using exact Access version as end-user
running, or at least lowest version, if they run multiple versions. No
problem (well, almost no) to run multiple access versions on same PC

I'm testing my 2007 applications with the new Beta version of Access
2010
and

[quoted text clipped - 21 lines]

Thanks,cw