Go Premium for a chance to win a PS4. Enter to Win

x
  • Status: Solved
  • Priority: Medium
  • Security: Public
  • Views: 1571
  • Last Modified:

.ade and .adp Access files

Hi all.

I'm looking at a .adp file that I'm not sure if it was worked on with Access 2003, 2007 or 2010. Access 2010 is currently installed on the one computer where the work is to be done while all the end users have an Access runtime to work with the .ade file.

Should I just edit it with Access 2010 and then create the .ade file?

I get 2 errors when trying to work with the .adp file in Access 2010:

"Your <<project name>> database or project contains a missing or broken reference to the file 'wiascr.dll' version 1.0"

and

"Your <<project name>> database or project contains a missing or broken reference to the file 'MSCAL.OCX' version 7.0"

Mind you, Access 2010 was just installed on this workstation where the work will be done.

Any help or guidance would be greatly appreciated.
0
printmedia
Asked:
printmedia
  • 4
1 Solution
 
Jim Dettman (Microsoft MVP/ EE MVE)PresidentCommented:
General rule of thumb has to always been create mde/ade's with the same version that the users are using.

<<"Your <<project name>> database or project contains a missing or broken reference to the file 'wiascr.dll' version 1.0">>

  That is a windows image aquistion .dll.  You'll need to find out where it came from.  You can try unchecking the reference and see of the app compiles.  It may be an old reference or not needed.

<<"Your <<project name>> database or project contains a missing or broken reference to the file 'MSCAL.OCX' version 7.0">>

 The calendar control does not come with Access as of 2010.  It was replaced with a date picker in Access.  You need to use the date picker or another calendar control.

 Do your users have the full retail version of Access or are they using runtimes?  If runtimes, I would update all to the A2010 runtime and develop in the same version.

  If not, then I would go back to A2007 on your station for development.

Jim.
0
 
Jim Dettman (Microsoft MVP/ EE MVE)PresidentCommented:
<<'wiascr.dll' >>

 I just double checked on this and it is the Windows Image Application Scripting lib and was part of windows XP.

Support for it stopped in Vista.  If your still using it, you're going to need to find another way of image handling in Windows Vista/7.

 I would buy a 3rd party control to replace it depending on what it is your doing.

Jim.
0
 
Jim Dettman (Microsoft MVP/ EE MVE)PresidentCommented:
0
 
printmediaAuthor Commented:
Could the calendar error be my answer, that this .ade was created from a .adp file created in Access 2007 and not Access 2010?
0
 
Jim Dettman (Microsoft MVP/ EE MVE)PresidentCommented:
<<Could the calendar error be my answer, that this .ade was created from a .adp file created in Access 2007 and not Access 2010? >>

 Most certainly something other then 2010.  Otherwise it would not have had the calendar control.

Jim.
0

Featured Post

Concerto Cloud for Software Providers & ISVs

Can Concerto Cloud Services help you focus on evolving your application offerings, while delivering the best cloud experience to your customers? From DevOps to revenue models and customer support, the answer is yes!

Learn how Concerto can help you.

  • 4
Tackle projects and never again get stuck behind a technical roadblock.
Join Now