Re: run time error 2113

This is the subroutine - the code fails on the second line which sets
Wholesale_Rate, and Outer & Split (different prices) are no longer
shown in the list box on the form:

Private Sub Item_BeforeUpdate(Cancel As Integer)

    Wholesale_Pack = IIf([Customer.Type] = "R" Or [Customer.Type] =
"S" Or [Customer.Order_Type] = "S", 2, 1)
    Wholesale_Rate = IIf(Pack = "1", Outer, Split)
    Wholesale_Ratio = Ratio
    Wholesale_Unit = Cost_Unit
    Wholesale_VAT = Rate
    Wholesale_Cost = Deld_Cost

    Occurs = 0

End Sub

I have now observed that on the 2 machines that fail, they only fail
if a particular pop-up form is opened and closed - if the pop-up form
is left open then no error occurs.  On the other 4 machines, no
failure occcurs even when the pop-up form is closed.  This specific
code has been in daily use for 3 years without any problems, but the
system as a whole is regularly updated in-house

Hope someone can help??


"TC" <[EMAIL PROTECTED]> wrote in message news:<[EMAIL PROTECTED]>...
> If you have access to the sourcecode, the smart move would be to add some
> error logging, to find the line of code on which this occurrs. Then take it
> from there, and/or, post that line & ask for further help.
> 
> HTH,
> TC
> 
> 
> "Alex Marsh" <[EMAIL PROTECTED]> wrote in message
> news:[EMAIL PROTECTED]
> > I have a LAN of 7 PCs running Access 2000. Recently the 2 newest PCs
> > with Athlon XP2000 and XP2400 CPUs have started to generate
> > intermittent but frequent run time error 2113 'data invalid for field'
> > during order-entry of valid product codes;  the problem seems to be
> > machine-specific as the users can immediately carry on working on any
> > of the other PCs.  As well as updating the software to O2K SR3 and Jet
> > SP7, and completely rebuilding the database, I've also swapped the
> > network ports around on the network switch (but I haven't swapped the
> > cables).  I'm wondering whether there could be a problem with the
> > on-board network adaptors. [Prior to rebuilding the database, there
> > had been some corruption in the VB code which had been lurking for
> > several months.]  The hardware supplier has concluded the problem is
> > software-related! All suggestions welcome!