But thanks to all - it turned into a great troubleshooting tutorial.
Bruce Chitiea SafeSectors, Inc. 909.238.9012 cell From: [email protected] [mailto:[email protected]] On Behalf Of Hodges, Dennis Sent: Wednesday, November 05, 2014 5:22 AM To: RBASE-L Mailing List Subject: [RBASE-L] - Re: Insert into not inserting all records Problem solved. This was a duuuuuh moment. It had nothing to do with the insert commands, I found the error further down the code in a delete duplicates statement. Dennis Hodges Maintenance Management Manager FDOT Office of Maintenance MS #52 PH: (850) 410-5635 FAX: (850) 410-5511 <mailto:[email protected]> [email protected] As far as we know, our computer has never had an undetected error. Please note: e-mail may be subject to public disclosure. From: [email protected] <mailto:[email protected]> [mailto:[email protected]] On Behalf Of Ken Shapiro Sent: Tuesday, November 04, 2014 10:14 PM To: RBASE-L Mailing List Subject: [RBASE-L] - Re: Insert into not inserting all records Hi, A few suggestions: - Turn set messages on and set error messages on and trace the code for errors - Check for a data mismatch and/or reload the database - Try an append and see if you get more than two rows - Try an insert with named columns and see if you get more than 2 rows. - Check the table for missing foreign keys and make sure any rules against RDA3 are valid. (If you try to reload the database you will find out if there is some data or corruption issue) Ken From: [email protected] <mailto:[email protected]> [mailto:[email protected]] On Behalf Of Albert Berry Sent: Tuesday, November 04, 2014 6:48 PM To: RBASE-L Mailing List Subject: [RBASE-L] - Re: Insert into not inserting all records To amplify the previous comments, your inserts into rda2, 3 and 4 are probably failing because you have a column mismatch. You have dropped the column chekval from rda1. Have you also dropped it from rda2, 3 and 4? If not the insert will fail because of the column mismatch as described by the other comments. Albert On 11/4/2014 10:23 AM, Hodges, Dennis wrote: I have a process that extracts a single day's records, edits them and reinserts them into the permanent file. I am running the following code in an EEP. Everything is working correctly except the next to last line (INSERT INTO daily3 SELECT * FROM rda3). The problem is that I can run this exact code from the r:Prompt and it works fine, which in my sample data replaces 2 records, but in the EEP it only inserts the first of the 2 records. I have reviewed the table columns, keys/indexes, rules and triggers and can find no conflicts, in fact the daily3 table has no rules, etc. All rules are applied to the rda3 table. Here is the segment of code in question. DELETE ROWS FROM daily1 WHERE datex EQ "11/15/14" AND (priflag EQ "Y" OR priflag EQ "X") DELETE ROWS FROM daily2 WHERE datex EQ "11/15/14" DELETE ROWS FROM daily3 WHERE datex EQ "11/15/14" DELETE ROWS FROM daily4 WHERE datex EQ "11/15/14" DROP COL chekval FROM rda1 INSERT INTO daily1 (crew, datex, units1, units2, units3, units4, cmpsite1, cmpsite2, cmpsite3, cmpsite4, cr_page, priflag) SELECT crew, datex, units1, units2, units3, units4, cmpsite1, cmpsite2, cmpsite3, cmpsite4, cr_page, priflag FROM rda1 INSERT INTO daily2 SELECT * FROM rda2 INSERT INTO daily3 SELECT * FROM rda3 INSERT INTO daily4 SELECT * FROM rda4 Dennis Hodges Maintenance Management Manager FDOT Office of Maintenance MS #52 PH: (850) 410-5635 FAX: (850) 410-5511 <mailto:[email protected]> [email protected] As far as we know, our computer has never had an undetected error. Please note: e-mail may be subject to public disclosure.
