On Thu, Jan 2, 2014 at 5:50 PM, Jeff Johnson <[email protected]> wrote:
> I am scanning a dbf and inserting records into a sql server table. For > some reason for the first half of the table it is skipping 440 records. > After half way through it is up to date. > Well, 440 isn't one of the magic numbers, unless you run track. (440 yards is one-quarter of a mile.) > Immediately after I load the table I do a select on it and that tells me I > skipped all of those records. > How is it that it tells you that? If you execute a select and after the select, there are less records, the logical implication is that you filtered them out. If you want to share the file structure and code, we can brainstorm it. I'd guess some NULLs snuck in there through an outer join, or you're missing records in a join condition. > I don't know if it skipped the records or my subsequent query is not > selecting all of the records. > Me, neither. -- Ted Roche Ted Roche & Associates, LLC http://www.tedroche.com --- StripMime Report -- processed MIME parts --- multipart/alternative text/plain (text body -- kept) text/html --- _______________________________________________ Post Messages to: [email protected] Subscription Maintenance: http://mail.leafe.com/mailman/listinfo/profox OT-free version of this list: http://mail.leafe.com/mailman/listinfo/profoxtech Searchable Archive: http://leafe.com/archives/search/profox This message: http://leafe.com/archives/byMID/profox/cacw6n4ufpntew+a8b1kdxgo+wwgqa+ahax0fgdfwgmzmdzt...@mail.gmail.com ** All postings, unless explicitly stated otherwise, are the opinions of the author, and do not constitute legal or medical advice. This statement is added to the messages for those lawyers who are too stupid to see the obvious.
