Albert, Thanks for the information. After hitting my head against the wall for most of the day, I realized I made my own mistake. I had consolidated some of my history tables during the Christmas break, but deleted one too many tables. That table was referenced by my order form and that is what caused the problem. Once I recreated the table, I was able to enter my orders properly.
Once a DB gets large, it is easy to forget things. Good thing I kept notes on my changes and was able to go back to the notes. James Belisle Making Information Systems People Friendly Since 1990 -----Original Message----- From: [email protected] [mailto:[email protected]] On Behalf Of Albert Berry Sent: Friday, December 27, 2013 6:03 PM To: RBASE-L Mailing List Subject: [RBASE-L] - Re: COMPILED APP PROBLEM I once had a similar problem when the index file went wonky and the PK was duplicating. Check that your autonumbering has not been fouled up. It's simple to reset it. SET VAR vPKValue INTEGER = NULL SELECT MAX(PKColName + 1 INTO vPKValue FROM (order table) AUTONUM PKColName IN ordertable USING .vPKValue, 1 Try entering an order. If it now works, you found it! If it works, check the rest of your autonumbered columns while you are in there. Albert On 12/27/2013 3:31 PM, Jim Belisle wrote: > > > Our compiled application has been working smoothly with no problems. > > I made no changes to the order entry code though I made slight changes > to other areas. > > Now I cannot enter orders at all. Earlier today I was able to enter on > my application. > > Anyone have any suggestions as to where I should look? > > > > It looks like sales has been able to enter the quotes are okay. > > > > James Belisle > > > > Making Information Systems People Friendly Since 1990 > > > > > >
