Solved

Access 2010 don't load forms correctly for .mde file

Posted on 2016-08-22
13
28 Views
Last Modified: 2016-08-22
Hi,

Some users are still using Access 2003. Nowadays I use the 2010 to develop new .mdb program versions. The .mdb file is copied to a 2003 system and a .mde file is created. The .mde works fine with 2003, but not any longer for 2010. The error is the following.

When most forms are loaded, access will ask for the parameter values that are used in the listboxs' queries. For example, "Enter Parameter Value" and the control name referenced to. Since it works for 2003 the name is correct and the control exists.

I am still using Dao 3.6. Beföre the creation of the .mde, the refercencies are the proper one. Notice that I use the dao 3.6 also in the 2010 version.

What is happening? I have never seen anything like this.

Thanks in advance

BAnders
0
Comment
Question by:BACapta
  • 8
  • 5
13 Comments
 
LVL 57
ID: 41765713
<<What is happening? I have never seen anything like this.>>

<<For example, "Enter Parameter Value" and the control name referenced to. Since it works for 2003 the name is correct and the control exists.>>

 Broken references and possibly 32 bit Office vs 64 bit Office.  Are all your Access 2010 users using 32 bit?   I'd start with that.

 References are harder to pin down in terms of fixing.

Jim.
0
 

Author Comment

by:BACapta
ID: 41765730
32-bits but win7 64 bits
0
 

Author Comment

by:BACapta
ID: 41765732
Sorry not all my users use 2010.
0
 
LVL 57
ID: 41765751
<<When most forms are loaded, access will ask for the parameter values that are used in the listboxs' queries. >>

 A2010 did tighten up on a lot of things internally; what kind of syntax are you using for the control reference?

Jim.
0
 

Author Comment

by:BACapta
ID: 41765756
Notice, I have put in msgbox in Form_open event at the beginning and the "Enter .." turn up before that event. So, it is while loading the controls.
0
 

Author Comment

by:BACapta
ID: 41765757
[Forms]![FormName]![ControlName] the same as you get using the Build Tool.
0
U.S. Department of Agriculture and Acronis Access

With the new era of mobile computing, smartphones and tablets, wireless communications and cloud services, the USDA sought to take advantage of a mobilized workforce and the blurring lines between personal and corporate computing resources.

 
LVL 57
ID: 41765765
Well syntax is OK.

<<Notice, I have put in msgbox in Form_open event at the beginning and the "Enter .." turn up before that event. So, it is while loading the controls.>>

  Are you doing anything in the form open event with the controls, like assigning rowsources?

Jim.
0
 

Author Comment

by:BACapta
ID: 41765779
The Rowsources are assigned at design.

I am not 100% sure, the problem was not around a week or so ago. I have run a .mde which was created a couple of weeks ago and that one worked,, not anylonger, same problem.

BAnders
0
 
LVL 57

Accepted Solution

by:
Jim Dettman (Microsoft MVP/ EE MVE) earned 500 total points
ID: 41765803
<< I have run a .mde which was created a couple of weeks ago and that one worked,, not anylonger, same problem.>>

  Has to be references then somehow...

  Put a copy of the MDB on a 2010 machine and open it (assuming your not using the run-time) and see if there are any problems with references.

  Watch it though; the basic references for Office/Access will auto update to the 2010 versions, so make sure you don't mix it up with what you use for A2003.

 If that works, then try making a MDE on with A2010 and test that.  If that works, then it's definitely references breaking in some way from the 2003 version.

Jim.
0
 

Author Comment

by:BACapta
ID: 41765889
To start with the last test creating the .mde with A2010. It works for A2010, but not for A2003. It will not recognize the database format. It is like that it can't handle the future referencies. Notice, it is a .mdb that has been created to .mde.

I have exported referencies via printscreen of a MsgBox, see attachement. I can't see any difference between the later two, and still one not work and the other one does.

BAnders
0
 

Author Comment

by:BACapta
ID: 41765922
Does not should it be. This is Ok for now. I will start to use package installation kits later on.

Many thanks.

BAnders
0
 

Author Closing Comment

by:BACapta
ID: 41765924
You always learn something new. I didn't know that you can create a mde from 2010, anyway not working on A2003.
0
 
LVL 57
ID: 41765978
Yes, you can create a MDE in any version of Access and it is recommended that you use a MDE that was created with the same version that your executing to avoid problems.

 Although for the most part, you can take a MDE from a prior version and run it in a later version. A2010 is a bit different in that it was the first version to have both 32 and 64 bit VBA and there was some issues with that early on when it compiled VBA code.   That may or may not have something to do with this (they made a few changes in VBA to accomplish that).

 A MDE by the way is nothing more than a MDB with the source code stripped out.

Jim.
0

Featured Post

Is Your Active Directory as Secure as You Think?

More than 75% of all records are compromised because of the loss or theft of a privileged credential. Experts have been exploring Active Directory infrastructure to identify key threats and establish best practices for keeping data safe. Attend this month’s webinar to learn more.

Question has a verified solution.

If you are experiencing a similar issue, please ask a related question

Suggested Solutions

In a multiple monitor setup, if you don't want to use AutoCenter to position your popup forms, you have a problem: where will they appear?  Sometimes you may have an additional problem: where the devil did they go?  If you last had a popup form open…
Modern/Metro styled message box and input box that directly can replace MsgBox() and InputBox()in Microsoft Access 2013 and later. Also included is a preconfigured error box to be used in error handling.
Familiarize people with the process of utilizing SQL Server stored procedures from within Microsoft Access. Microsoft Access is a very powerful client/server development tool. One of the SQL Server objects that you can interact with from within Micr…
In Microsoft Access, learn different ways of passing a string value within a string argument. Also learn what a “Type Mis-match” error is about.

947 members asked questions and received personalized solutions in the past 7 days.

Join the community of 500,000 technology professionals and ask your questions.

Join & Ask a Question

Need Help in Real-Time?

Connect with top rated Experts

23 Experts available now in Live!

Get 1:1 Help Now