2002 ADP versus 2003 ADP

[Carl]

I am using SQL 2000 as a backend and designed in Access
2003 ADP.
This particular issues is working fine in Access 2003 ADP
but when I went to run it on a client machine running
Access 2002 ADP (which supposedly there are no
compatibility issues) I am receiving the following error
message which debugs to the following After_Update event
when I try to update a subform.

Run-Time error -2147417848 (80010108)
Method 'Controls' of object '_Subform'failed

This is the After_Update event:
Private Sub QtyRqdX_AfterUpdate()
Me!QtyRqdEa = CheckQtyX(Me!QtyRqdX, Me.Parent!
sfmPOItem!PerCase)
If F_QtyRqdEa <> Me!QtyRqdEa Then
Me.Parent!sfmPOItem!QtyRqdEa = Me.Parent!sfmPOItem!
QtyRqdEa + Me!QtyRqdEa - F_QtyRqdEa
Me.Parent!sfmPOItem.Form.ExtendOrderLine
F_QtyRqdEa = Me!QtyRqdEa
End If
End Sub

This is not going to be good when implementing this
application on our companies client machines.....anybody
have any ideas???

 

[Sylvain Lafontaine]

First, you should reactivate the error control in Access to have the exact
line who is the offender.

Second, it's look like to me that maybe this is because you have forgotten
to add the .Form! after the name of some of your subforms; but I didn't take
the time to build a test form, so I'm not sure if it's mandatory in Access
2002.

Using the /decompile /compact switchs before distributing your application
may also be a good idea.

S. L.

 

[Carl]

I tried to use the .form! to referrence the subform and
that does not make any difference.
The line that the code is breaking on is:

Me.Parent!sfmPOItem!QtyRqdEa = Me.Parent!sfmPOItem!
QtyRqdEa + Me!QtyRqdEa - F_QtyRqdEa

Does anyone know if 2003 ADP's are compatible with 2002
ADP's because I hope I am not going down the wrong road
here???

 

[Sylvain Lafontaine]

There are different products, so it's impossible to claim that they are 100%
compatible but, except for some added events, they should be compatible for
almost everything else.

Your VBA code below seems pretty standard. As you are changing a value
inside another subform from one subform, the only thing that come to my mind
is that this other subform is in some way unavalaible when you try to change
it. I have nothing that came come to that at this moment, but I will try to
make some tests this weekend.

I have not Access 2003 at this moment, so I cannot tell you more about
compatibility issues.

(Of course, I presume that sfmPOItem is the name of the control which
contains the subform, not the name of the subform itself; as it is possible
to me that Access 2003 may be able to find the control from the name of the
subform. As I don't have it at this moment, I cannot be totally sure that
it cannot make this kind of stuff.)

In any case, maybe you could buy the Access 2003 runtime and distribute it
with your application?

S. L.