Thanks Javier,

I thought that the saverow caused a new record to be written to disk and I
thought that POST applied to rows that are edited.  However, I admit that I
am unclear on how the buffer flow takes place in RBASE.  I will give POST a
try.

 

I am groping at straws, it doesn't seem logical that you could print the
data to a report without it being saved on the disk.  I expected to find a
rogue DELETE command in the code but there are no DELETES in play.

 

I did check prior threads but I did not see any that shed light on my
situation.  I will try the POST and I will write a trap to see if I can
gather enough information to solve the puzzle. 

 

John Engwer

(412) 751-2433

 

From: [email protected] [mailto:[email protected]] On Behalf Of Javier
Valencia
Sent: Tuesday, May 10, 2011 5:38 PM
To: RBASE-L Mailing List
Subject: [RBASE-L] - RE: Missing records

 

John,

 

There have been a few threads on this topic; you might try searching the
archives. In the mean time, you might try:

 

PROPERTY TABLE PURCHASE 'POST' 

 

To do the actual writing to disk.

 

Javier,

 

Javier Valencia, PE

913-829-0888 Office

913-915-3137 Cell

913-649-2904 Fax

 <mailto:[email protected]> [email protected]

 

  _____  

From: [email protected] [mailto:[email protected]] On Behalf Of John Engwer
Sent: Tuesday, May 10, 2011 4:04 PM
To: RBASE-L Mailing List
Subject: [RBASE-L] - Missing records

 

Latest release of V8 compiled

 

I have a routine that generates an invoice for a point of sale application.
A few weeks ago, one of my clients reported that he printed an invoice that
included three line items.  Moments after printing the invoice he displayed
a copy of the invoice on the screen and the last line item was missing.  I
checked the "Purchase" file and verified that the line item was missing and
I saw a copy of the purchase record that he printed.  Today, I had a second
client report the same type of failure.

 

The purchase file contains an invoice number and a transaction number.  The
transaction number is an auto number. 

 

Here is the process:

The line items are entered into the PURCHASE file via a scrolling region.  

When they are finished entering items they click a bit button that saves the
data (saverow), does some other housekeeping and then goes to a checkout
form where the user enters the payment method and prints the invoice.

The invoice is a report based on the PURCHASE and CUSTOMER tables.

 

I thought that the data was getting hung up in a buffer so I added  PROPERTY
TABLE PURCHASE 'UPDATE' before the SAVEROW.  However, It has occurred one
time since I added the "Update".   As a troubleshooting tool, I am going to
write a duplicate purchase record in an audit file until I get this issue
resolved.  I think the data must be written to disk or the data would not
show up on the printed record.  I scanned all of the code and I cannot find
any delete rows in the that can cause a record to be deleted.

 

Any ideas or comments will be appreciated.

 

John 

 

Reply via email to