Pat - thanks - makes sense to me. I forgot all about the ::J options and even if I had remembered, wouldn't have thought to use it to solve this issue.
2011/3/4 Patrick Riley <[email protected]> > Don, your theory is likely correct as the ::I mode does not increment > until the record is written potentially allowing a second import record to > be read during the write cycle and grab the same index value. > > Changing the DataPerfect auto-increment mode from ::I (at save) to ::J > (at initiation) would likely avoid the crashes you're seeing. I've > imported > over 2,000,000 records in a sigle process using an ::J auto-increment > index field without issue. > > Pat Riley > > > > At 09:05 PM 3/3/2011, Don Friedman wrote: > > Hi Tim. The imported data crashed at various points ranging from about > 3,000 in to 9,000 in. In years past I've seen some sketchy data that had > some junk interspersed in it and had to clean it up before importing > successfully but in this case the data was perfectly clean. As it was all a > .csv file that I had already had in a spreadsheet, I opened it up again and > added a column with consecutive numbering, used that field as an index and > the data then imported perfectly. > > Which makes me wonder if perhaps the ::I file can't generate as fast as the > new processors can pump the data in and if that could be an issue. Once I > removed the ::I everything worked perfectly. > > Don > > > > 2011/3/3 Tim Rude <[email protected]> > Don, > > How many records got imported before it failed each time? > > Tim Rude > ----- Original Message ----- > From: Don Friedman <[email protected]> > To: Dataperfect Users Discussion Group <[email protected]> > Sent: Thursday, March 03, 2011 1:53 PM > Subject: [Dataperf] Problem with incrementing number > > I was working with a small database today (a county with only about 91,000 > voters) and at a certain point I attempted to create a new panel and import > a .csv file with about 17,000 lines of data using an incrementing GZZZZZ > field as an index. Every attempt to import the data failed before completion > so I tried creating the panel again, exporting and importing the .ste file > and re-creating indexes. No luck. > > Inspected raw data. Looked fine. > > Created a stand-alone database with a single panel for this application. > Again, import kept failing. > > Failing to come up with a credible reason why it wasn't working I added an > index number to the data set so that rather than depending on the > incrementing number, the data would have its own unique number. That did the > trick. > > Any ideas as to why? > > Don Friedman > > > -- > Don Friedman > ProfessionalRecords.Com LLC > PRS Data Systems > 205 S Main Street > Pittsburgh, PA 15215 > 412-784-1600 - 1-800-PRS-FILE > 412-784-1615 Fax > > ------------------------------ > _______________________________________________ > Dataperf mailing list > [email protected] > http://lists.dataperfect.nl/mailman/listinfo/dataperf > > > _______________________________________________ > Dataperf mailing list > [email protected] > http://lists.dataperfect.nl/mailman/listinfo/dataperf > > > > > -- > Don Friedman > ProfessionalRecords.Com LLC > PRS Data Systems > 205 S Main Street > Pittsburgh, PA 15215 > 412-784-1600 - 1-800-PRS-FILE > 412-784-1615 Fax > _______________________________________________ > Dataperf mailing list > [email protected] > http://lists.dataperfect.nl/mailman/listinfo/dataperf > > > _______________________________________________ > Dataperf mailing list > [email protected] > http://lists.dataperfect.nl/mailman/listinfo/dataperf > > -- Don Friedman ProfessionalRecords.Com LLC PRS Data Systems 205 S Main Street Pittsburgh, PA 15215 412-784-1600 - 1-800-PRS-FILE 412-784-1615 Fax
_______________________________________________ Dataperf mailing list [email protected] http://lists.dataperfect.nl/mailman/listinfo/dataperf
