Call me lazy, but I agree with Clayton's sentiments, at least from a quick-and-dirty, management-by-exception perspective.
My (Surely Less Than) $0.02, Steve in Memphis From: [email protected] [mailto:[EMAIL PROTECTED] On Behalf Of Bill Downall Sent: Tuesday, January 15, 2008 9:31 AM To: RBASE-L Mailing List Subject: [RBASE-L] - RE: Importing data using Gateway Clayton, What did you do with the exception file in old R:BASE? You still had to do something with those rows that failed to load. To my mind, using Jeff's approach with the newer gateway gives you the best of both worlds: You can a) get all the data you need into the database, and b) determine programmatically exactly what would fail and exactly why it would fail. Old way, you still had to account for and deal with your exception file in some way. New way you can actually correct some of those things on the way in, report to your vendor the errors they are making, and log what you need to. I think in both scenarios you have to use a combination of PC brain and human brain :) Bill On 1/15/08, Clayton ANDERSON < [EMAIL PROTECTED] <mailto:[EMAIL PROTECTED]> > wrote: So turn off the PC brain and trust the human to get it right?? Not much of a solution. Does this need to be sent to the request for enhancement group?? >>> "Jeffrey M. Watson" <[EMAIL PROTECTED]> 1/15/2008 7:25 AM >>> I have noticed the same behaviour, but what you can do is load your data to a temporary table with no rules and keys. once it is loaded you can 'clean' the data as needed, and append / select+insert it into the desired table. Hope this helps. -Jeff Jeff Watson [ [EMAIL PROTECTED] Tube Methods, Inc. 610-279-7700 -----Original Message----- From: [email protected] [mailto:[EMAIL PROTECTED] On Behalf Of Clayton ANDERSON Sent: Tuesday, January 15, 2008 9:20 AM To: RBASE-L Mailing List Subject: [RBASE-L] - Importing data using Gateway The old RBase (DOS 4.5) handled exceptions during data importing with the Gateway and placed the exceptions into a except.dat file. Version 7.6 seems to just stop when coming across and rule violation. Any way to have it continue and/or handle exceptions??
