I have a form (Edit using...) that has an EEP containing "NEWROW", that adds
a new row, when necessary. The row contains an integer autonumber column
that is indexed.
Users get to the "newrow" OK and when they "Exit from a row", there is an
EEP that does an update on the row (using the autonumber column in the where
clause in the update) .
Everything works fine 99.99% of the time, however, every so often the EEP
returns error 2059 ("No rows exist or satisfy the specified clause"). I
have put in code in the EEP that looks at selected variables/values when
this error happens and the info seems OK (The row actually seems to be
there). This problem only seems to happen with the fastest entry people
during the busiest part of the day.
This problem Never happens when they are editing previously existing rows.
Since the referenced column is indexed, I was wondering if there might be
some significant lag time in creating the index and thus even though the row
exists, the where clause can't find it because the indexing hasn't
completed.
Am running RB DOS 6.5++ with WIN2000 OS
Programs seem to execute slower with our WIN2000 server than with our old
Novell server. Could this "speed down" be a factor?
Any thoughts?
Frank Radice
[EMAIL PROTECTED]
