The EEP that has the NEWROW command DOES have a SCREEN RESTORE OFF. This
EEP executes when leaving the last field on the form. If there is another
row then it just goes to the next row. If the row you are in is the Last
row, then it adds a New Row and then goes to that new row.
Creating & editing the row is NOT the problem. The user gets to the new row
and enters data. However, if I put ANY command with a WHERE clause (such as
SEL...WHERE...) in the EEP that runs when you "Exit the row", and I
reference the "Indexed autonumber column" in the where clause, then it finds
the desired row OK MOST of the time but it FAILS (No rows satisfy...) about
1 in 500 times. Again, this is usually during the busy part of the day and
with the fastest data entry people. There may be a max of 40 users on the
network, in the database at one time.
I think that I may have experienced a related problem a while back. I
inserted a row that had an index and immediately went to an ajoining
computer to display the info (SEL ALL FRO Customer WHERE Cust = 91228) but
it said that there were no rows that satisfy the where clause. I tried it a
few seconds later and the row showed up. Seems like there is an indexing
lag??
I don't remember having this problem when this application ran under RB
4.5++ on the Novell server.
-----Original Message-----
From: A. Razzak Memon [mailto:[EMAIL PROTECTED]]
Sent: Friday, September 07, 2001 6:11 PM
To: [EMAIL PROTECTED]
Subject: Re: Indexing speed - Razzak's Reply
Frank,
To see the effect of the NEWROW command, you must include
the SCREEN RESTORE OFF command in the EEP.
Have Fun!
Very Best Regards,
Razzak.
At 05:20 PM 9/7/2001 -0700, Frank Radice wrote:
>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?
===================================-============================
R:BASE Developers's Conference: http://www.rbase.com/conference
Official R:BASE List Server: mailto:[EMAIL PROTECTED]
RBTI Events/Training: http://www.rbase2000.com/events
R:DCC Members: http://www.rbase2000.com/rdcc
================================================================
R:BASE, Oterro & R:Tango are registered trademarks of RBTI.
==================================-=============================
