First things first, longtime database geek, first time FM user.

Inherited an app to manage wirelist, along with the template files used to construct tables. I've input data to our facility's wirelist and now (don't know specifically what I did) labels don't print correctly. Template file still prints correctly, but any records I import (as .fp5 records) won't.

On the import, I've unchecked any fields having to do with report/label settings, yet the corruption still occurs. While I'll try a .csv import, is there some way to figure out what I've done to formatting, structure, etc. (?) that might cause this problem?

With 8k records, I'd rather not rebuild this from scratch and, frankly, I'm not making the greatest of first impressions in my new job. Any help appreciated.

Thanks,

Geoff.

I'm a little confused, are you importing from a csv or a FileMaker file? I have found that importing from a Tab Delimited file works better than csv (those pesky commas hidden somewhere in the data can wreck havoc).

Also, what specifically are your labels doing during printing?

Mike

Sorry for the confusion, here's the poop. I figured that the 'template' structure is ok, since I'm able to print records from it that are ok. I emptied (a copy of) the template table and imported FM records, unchecking any fields having to do with labels (in the import field match dialog). Label printing is then a no-go. Re-copied template, left its records intact, and imported only a few records from the original table. NG. So the .csv question was just a thought I had to import records stripped of any formatting that might be screwing up the print jobs.

As to the labels, they come out of a Brady thermal printer and the labels are on a long roll, printed one at a time (not 2,3,4 across). Orientation of labels is that the printable area is on the left hand side, approx 3/4" wide and 2" long. Print gets rotated so that the 2" side becomes the width. Structure of the print is as follows:

<Field1><Field2><Field3>

<Field1><Field4><Field5>

<Field1><Field2><Field3>

<Field1><Field4><Field5>

Bad labels come out with 'Field1' missing and only half (if we're lucky) of Fields 2 and 4. No jiggering of the printer settings will correct the misprint.

Hope that's a bit clearer, and even more that it sparks an idea.

Thanks,

Geoff.

"....imported FM records, unchecking any fields having to do with labels (in the import field match dialog)."

You imported records but not the fields that you need to print?!?!?

Are Field1/2/3 etc. basic Text fields and not Calculation fields?

Paul J.

Sorry Paul, I re-posted under another topic and missed your reply.

No, the fields of data I need to make the labels I've imported. But there are, apparently, fields in the database having to do with the specs of the labels, and _those_ I have not brought across.

As to text v. calc, it appears to be text. However, the first field is a cable number, which can be incremented. As I can't access the structure of the tables, I'm assuming it's alphanumeric and the increment isn't, strictly speaking, a calculation.

Thanks,

Geoff.