1 person found this helpful
CS was soemtimes flakey in this way with Data Merge.
Are you updated to the latest patch? Most issues were resolved at some point.
That said, I recall another user with this problem, and it never resolved with his particular file. I examined the data file and couldn't find any issues, but it behaved identically on my system tot he way it did on his so I can only conclude there was still some bug, or something about the data file that we were unable to detect. I seem to recall that the same data file merged correctly in CS3, but I don't recall if I saved it long enough to test in CS5. I've not had any issues with my own files in any version.
Open the file in a plain text editor and look for any odd characters (I'd start the search where the merge first fails). Also do a Save As from the text editor to make sure there is no possibility of formatting from your spread sheet having found its way in.
Thanks, Peter. I'm up to CS5.5 now, but I haven't used the data merge feature with it yet. Even in CS4, I couldn't reproduce the problem.
As far as odd characters, the address1 field sometimes has double quotes around it when there is a comma in the field. But, again, it's not consistent for all the records that were merged incorrectly. There doesn't appear to be any spaces or weird paragraph breaks.
In any case, it sounds like some bugginess since you were able to reproduce it. I can't reproduce it. It's impossible to verify the data merge is correct (too much data!) so I may have to think of another solution for my variable data needs. Got in big trouble with my client because of this!
I would inspect the CSV file very carefully, perhaps in a hex editor. There may be nonprintable characters that are causing this problem.
Also, is it possible that you have an odd number of double-quotes somewhere right before this problem?
as john said, could be non-printing characters, but i'd suspect there was a comma in an address in the database somewhere, which has "fooled" indesign into thinking there is a field where there shouldn't be one.
rather than use csv, i tend to use a tab-delimited txt file from excel so that i can include commas in the database.
that's about all i could think of.
Sort of damned-if-you-do, damned-if-you-don't. If you use tab-delimited,
then you can't have tabs. If you use CSV, you can have commas as long as
they are on double-quotes. But you can't have double-quotes. Etc. etc.