• Status: Solved
  • Priority: Medium
  • Security: Public
  • Views: 74
  • Last Modified:

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

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
BACapta
Asked:
BACapta
  • 8
  • 5
1 Solution
 
Jim Dettman (Microsoft MVP/ EE MVE)PresidentCommented:
<<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
 
BACaptaAuthor Commented:
32-bits but win7 64 bits
0
 
BACaptaAuthor Commented:
Sorry not all my users use 2010.
0
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.

 
Jim Dettman (Microsoft MVP/ EE MVE)PresidentCommented:
<<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
 
BACaptaAuthor Commented:
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
 
BACaptaAuthor Commented:
[Forms]![FormName]![ControlName] the same as you get using the Build Tool.
0
 
Jim Dettman (Microsoft MVP/ EE MVE)PresidentCommented:
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
 
BACaptaAuthor Commented:
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
 
Jim Dettman (Microsoft MVP/ EE MVE)PresidentCommented:
<< 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
 
BACaptaAuthor Commented:
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
 
BACaptaAuthor Commented:
Does not should it be. This is Ok for now. I will start to use package installation kits later on.

Many thanks.

BAnders
0
 
BACaptaAuthor Commented:
You always learn something new. I didn't know that you can create a mde from 2010, anyway not working on A2003.
0
 
Jim Dettman (Microsoft MVP/ EE MVE)PresidentCommented:
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

Fill in the form and get your FREE NFR key NOW!

Veeam is happy to provide a FREE NFR server license to certified engineers, trainers, and bloggers.  It allows for the non‑production use of Veeam Agent for Microsoft Windows. This license is valid for five workstations and two servers.

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