RunTime version versus Full Version of Access
I have recently deployed an app where several users will only have the 2010 RunTime version of Access installed. One of those users is seeing things that I don't see. When a selection is made in a combo box she is getting the dialog box that one would see from a parameter query. For example, she gets a box asking for this value: [Forms]![frmLocation]
Lucian Constantin
Check the code to see if there are some "other" options if the application is running in the "runtime" or "full version" - maybe the developper did some tests and put something that could be related to the "development" environment.
<<When I open the file using RunTime everything works just fine. The same is true for other users as well. Any ideas what could be happening?>>
All that error is basically telling you is that at the time the query runs, Access can't figure out what that parameter reference pertains to, so it prompts you for a value.
This could be a mistake in the application itself or possibly something with their install (such as references being broken). I doubt it's related to the runtime itself.
However you can easily check that by running a copy of the DB along on your machine with a full version by using the /runtime switch on the command line.
Or if this is 2007 and up, you can rename the DB as .accdr, which will force runtime mode as well.
Jim.
All that error is basically telling you is that at the time the query runs, Access can't figure out what that parameter reference pertains to, so it prompts you for a value.
This could be a mistake in the application itself or possibly something with their install (such as references being broken). I doubt it's related to the runtime itself.
However you can easily check that by running a copy of the DB along on your machine with a full version by using the /runtime switch on the command line.
Or if this is 2007 and up, you can rename the DB as .accdr, which will force runtime mode as well.
Jim.
ASKER
Yes, I checked it on my machine by using the /runtime switch on the command line. That's what I was referring to when I said <<When I open the file using RunTime everything works just fine.>>
She did have issues early on that required a reinstall of Access 2010 Runtime. I'm assuming there is no way to check for missing references in the Runtime environment...right?
Could it be a timing issue with her machine? It's an older laptop running XP.
<< This could be a mistake in the application itself>>
I have no idea where to look for anything since it seems to be running just fine on other machines.
She did have issues early on that required a reinstall of Access 2010 Runtime. I'm assuming there is no way to check for missing references in the Runtime environment...right?
Could it be a timing issue with her machine? It's an older laptop running XP.
<< This could be a mistake in the application itself>>
I have no idea where to look for anything since it seems to be running just fine on other machines.
<<She did have issues early on that required a reinstall of Access 2010 Runtime. I'm assuming there is no way to check for missing references in the Runtime environment...right?>>
Not with the runtime, no. You need the full version so you can open the VBA editor. You'd need to do it within the app code itself.
<<Could it be a timing issue with her machine? It's an older laptop running XP.>>
Quite possibly. That is basically along the lines of what I suggested; at the time the query runs, the form with the control is not available, so she gets prompted. Whether that's due to timing or simply a bug in the app (i.e. she closed the form and it allowed her to) is hard to say. Only thing that's know is Access (actually the JET expression service) cannot resolve the reference.
<<I have no idea where to look for anything since it seems to be running just fine on other machines. >>
I would look to timing then...
Jim.
Not with the runtime, no. You need the full version so you can open the VBA editor. You'd need to do it within the app code itself.
<<Could it be a timing issue with her machine? It's an older laptop running XP.>>
Quite possibly. That is basically along the lines of what I suggested; at the time the query runs, the form with the control is not available, so she gets prompted. Whether that's due to timing or simply a bug in the app (i.e. she closed the form and it allowed her to) is hard to say. Only thing that's know is Access (actually the JET expression service) cannot resolve the reference.
<<I have no idea where to look for anything since it seems to be running just fine on other machines. >>
I would look to timing then...
Jim.
<One of those users >
Only One?
Is this users system identical to all the others in terms of hardware, Software versions, Updates and Service Packs...?
Only One?
Is this users system identical to all the others in terms of hardware, Software versions, Updates and Service Packs...?
ASKER
This app has just been rolled out and I've not heard of any other users having any issues. There will be about 50 users. I would highly suspect very few of the users (if any) have identical machines.
There are no missing references in my development version.
All forms are available when the control is selected. The control is on the main form and references 2 of the 4 subforms on the main form. So, availability is not the issue. Maybe the subforms are in the process of updating.
"Wait a minute", I just thought of something. These combo boxes are used to drill to a specific level of the data and are enabled as the user makes a selection.
For example:
Region combo box is always enabled.
Team combo box is enabled once a selection is made in Region combo box. It's then requeried to only include Teams within the selected Region. (This is probably the first parameter dialog box that shows up.)
Territory combo box is enabled once a selection is made in Team combo box. Then required based on the Territory. (This is probably the other dialog that pops up)
Do you think it would help if I move the firing of the requery from the AfterUpdate of Region combo box to the OnClick of the Team combo box...and so on.
There are no missing references in my development version.
All forms are available when the control is selected. The control is on the main form and references 2 of the 4 subforms on the main form. So, availability is not the issue. Maybe the subforms are in the process of updating.
"Wait a minute", I just thought of something. These combo boxes are used to drill to a specific level of the data and are enabled as the user makes a selection.
For example:
Region combo box is always enabled.
Team combo box is enabled once a selection is made in Region combo box. It's then requeried to only include Teams within the selected Region. (This is probably the first parameter dialog box that shows up.)
Territory combo box is enabled once a selection is made in Team combo box. Then required based on the Territory. (This is probably the other dialog that pops up)
Do you think it would help if I move the firing of the requery from the AfterUpdate of Region combo box to the OnClick of the Team combo box...and so on.
<This app has just been rolled out and I've not heard of any other users having any issues. There will be about 50 users. I would highly suspect very few of the users (if any) have identical machines.>
Then can you identify what might be different about this one users machine...?
Then can you identify what might be different about this one users machine...?
<<There are no missing references in my development version.>>
Understand that references working correctly are dependent on the machine the DB is running on, so it's quite possible that everything is fine on yours, but not on theirs.
I would think though that if references were broken, you'd be have more problems then this.
<<Do you think it would help if I move the firing of the requery from the AfterUpdate of Region combo box to the OnClick of the Team combo box...and so on.>>
I would leave it in the AfterUpdate. If you move it to the Enter or GotFoucs event, you'll be re-firing the requery every time. Only time it needs to change is when the combo it relies on changes.
Jim.
Understand that references working correctly are dependent on the machine the DB is running on, so it's quite possible that everything is fine on yours, but not on theirs.
I would think though that if references were broken, you'd be have more problems then this.
<<Do you think it would help if I move the firing of the requery from the AfterUpdate of Region combo box to the OnClick of the Team combo box...and so on.>>
I would leave it in the AfterUpdate. If you move it to the Enter or GotFoucs event, you'll be re-firing the requery every time. Only time it needs to change is when the combo it relies on changes.
Jim.
ASKER
Maybe a dumb question:is it possible to have a missing reference in a RunTime environment? If so, how would you know or fix it?
ASKER CERTIFIED SOLUTION
membership
This solution is only available to members.
To access this solution, you must be a member of Experts Exchange.