Importing csv files

[ken donco]

When importing csv files into Peachtree Complete from Filemaker, duplicate records are created, but were not present in the .csv file. I opened one of these files in Notepad and noticed all of the text records were bounded by double quotes ("). I exported some records from Peachtree and again opened this file in Notepad. No quotes were present around the data. I then deleted all of the quote marks in the first import file and imported the records again. This seemed to work correctly. Could this be the cause of the duplication of records in Peachtree? Has anyone else tried this?

[LauraG]

The import process sees "ABC" and ABC as 2 different records which is what is causing your duplicate records.

You should look at the exporting options in filemaker to see if you can eliminate the "" being used as a delimiter. You want commas instead of quote marks.

[Lisa_p]

You might try using Excel instead of notepad to look at your text file. You can clean it up in Excel (get rid of ") and save as a CSV.

[jwilfong]

In importing csv files I ran across a bug (PT2006) where once all the records in the csv had been read during import it would start all over again at the first record. If you see the asteriks going by then get an error in the first record, which could physically be multiple records in a csv as more than one csv record makes up a PT record, you may be seeing this bug. What I do is wait till I get the error then cancel the import. All records will be there only once. If you continue past this error you will get duplicate records.

--
John

[LauraG]

I just created a new company file using PT 2006 complete by importing everything I need from the old company and did not run into any problems with the imports.

Do you have any idea as to what "triggers" your bug to occur?

[gale]

Watch out for the NUMBER OF DISTRIBUTION column. That is the reason i know of for the so called BUG.

[jwilfong]

Do you have any idea as to what "triggers" your bug to occur?

Actually no. If you import all fields allowed by PT the bug will not surface. If you use only the fields specified as required in the PT help the bug appears. I have program that I created and used for years that utilizes the import facility of Peachtree and creates a file with all required fields. This is how I found it. I beta tested for PT2006 and provided a test case to PT to demonstrate the bug which was verified by PT. This bug did not appear in earlier versions and hopefully is gone in the up coming PT2007.

John

[jwilfong]

Watch out for the NUMBER OF DISTRIBUTION column. That is the reason i know of for the so called BUG.

Umm, No. If the number of distributions is incorrect you should receive a legitimate error. This is not a bug but a correct reporting of a problem with what Peachtree is expecting to see. The bug I'm talking about is an actual repeat of the import process. It doesn't matter whether 1 record is imported or 100's. If you cancel on recieving the error I'm referring to you will see every record imported correctly. If you cancel on a number of distribution error you will either see no records imported or only records up to the point of the error imported.

John