C
cg084
All,
I am in the process of migrating .adp and .ade projects developed in Access
2003 to Access 2007. At present the Office 2007 application is being rolled
out in phases to company employees. So there is a period where 2 versions of
Access are being used. As the project is about 80% .ade files this raises a
concern to me when the files are worked upon and the .ade file has been
created using Access 2007 when a user attempts to open the .ade file in
Access 2003. I have reason to believe this is due to the Access 12 Object
Library.
Has anyone had this problem?
Does anyone know of a workaround to this problem. It kind of defeats the
purpose of migrating Access 2003 .adp and .ade files to the latest version
when not everyone is up and running with Access 2007, when i still have to
make the .ade file using the Access 2003 application.
I am in the process of migrating .adp and .ade projects developed in Access
2003 to Access 2007. At present the Office 2007 application is being rolled
out in phases to company employees. So there is a period where 2 versions of
Access are being used. As the project is about 80% .ade files this raises a
concern to me when the files are worked upon and the .ade file has been
created using Access 2007 when a user attempts to open the .ade file in
Access 2003. I have reason to believe this is due to the Access 12 Object
Library.
Has anyone had this problem?
Does anyone know of a workaround to this problem. It kind of defeats the
purpose of migrating Access 2003 .adp and .ade files to the latest version
when not everyone is up and running with Access 2007, when i still have to
make the .ade file using the Access 2003 application.