D
Dave C
I thought I was ready to start deploying an application I've been working on
the for past year -- think again! It won't run under the Access 2007 Runtime.
I'm using the newly released Access 2007 Runtime version 2.
The first problem was with having function names specified as an event
property. (For example =HandleButton(1) as the event, instead of [Event
Procedure] and a procedure in the module MyButton_Click() that calls
HandleButton 1. What upset me most about this is that it was a form Access
created for me (the switchboard) that I had to fix.
The second one -- the one that really has me worried -- has to do with sub
forms. It's effecting a large number of forms in my project. The sub forms
don't show. Works perfect in the full version of Access, and perfect with
the /Runtime switch on the development machine with Access installed.
Doesn't work on a machine that only has the Runtime.
I can't find any documentation on this bug. There's lots of talk about a
problem with subforms if the subform is pulling data from a remote data
source, but that's not the case here. Both form and subform are pulling data
from local tables. Both are bound forms.
I'm sure something's I've done that's setting these forms apart from normal,
because I can't believe MS would have missed something as basic as a
form/subform relationship when creating the runtime and its version 2.
Could it possibly be that the form is called with acDialog? Some property
in the subform's original definition that's ignored in the full version, but
that the runtime trips over?
Desperate for any suggestions at this point.
the for past year -- think again! It won't run under the Access 2007 Runtime.
I'm using the newly released Access 2007 Runtime version 2.
The first problem was with having function names specified as an event
property. (For example =HandleButton(1) as the event, instead of [Event
Procedure] and a procedure in the module MyButton_Click() that calls
HandleButton 1. What upset me most about this is that it was a form Access
created for me (the switchboard) that I had to fix.
The second one -- the one that really has me worried -- has to do with sub
forms. It's effecting a large number of forms in my project. The sub forms
don't show. Works perfect in the full version of Access, and perfect with
the /Runtime switch on the development machine with Access installed.
Doesn't work on a machine that only has the Runtime.
I can't find any documentation on this bug. There's lots of talk about a
problem with subforms if the subform is pulling data from a remote data
source, but that's not the case here. Both form and subform are pulling data
from local tables. Both are bound forms.
I'm sure something's I've done that's setting these forms apart from normal,
because I can't believe MS would have missed something as basic as a
form/subform relationship when creating the runtime and its version 2.
Could it possibly be that the form is called with acDialog? Some property
in the subform's original definition that's ignored in the full version, but
that the runtime trips over?
Desperate for any suggestions at this point.