Randy, Am I correct in that you are creating 20 rows in a dummy table with just an order no. and entering the region in edit mode instead of entry mode? and then you have to move the data from the dummy table to the real order entry tables? I have an ordhdr table for basic customer data and an orddtl table for the region. I have no trouble with F7 or F8 or extending the line cost. Just can't seem to eliminate the next row's ghosts in 2 places, of course it diappears as soon as they enter an item no in that row but sometimes they get locked up and can't get into the next row or go back with F7. But they can move back and forth in the current row. Sometimes if they move back to the item no. and rekey it, it then allows them to proceed to the next row. I can't reproduce it in order to try and solve the problem. I thought RESETROW would restore the original default settings where price is 0.00, but it doesn't -- I don't think I understand where to use resetrow.
I plan to be at the conference in April and if I can borrow a laptop, I will bring my app. (or maybe put it on a zip disk and see if someone will let me use their laptop). Bernie Lis Megabytes, Inc. > Rather than operate on a 'live' table, we use a >temporary table which only > represents the detail for that one invoice. The region works perfectly. When > it has all been entered, calculated and reviewed, the 'header' information is > inserted into a salesOrder table with SalesOrderID as the primary key. > ================================================ TO SEE MESSAGE POSTING GUIDELINES: Send a plain text email to [EMAIL PROTECTED] In the message body, put just two words: INTRO rbase-l ================================================ TO UNSUBSCRIBE: send a plain text email to [EMAIL PROTECTED] In the message body, put just two words: UNSUBSCRIBE rbase-l ================================================ TO SEARCH ARCHIVES: http://www.mail-archive.com/rbase-l%40sonetmail.com/
