Prinect and CIP files

[David]

if the names are the same, how are you ending up with it not overwriting the previous file?

sorry, I think I'm confused.     

[Joe]

if the names are the same, how are you ending up with it not overwriting the previous file?

sorry, I think I'm confused.     

Welcome to the club.

[David]

all right!
a new club!

when do we have meetings and are refreshments served?

[G_Town]

if the names are the same, how are you ending up with it not overwriting the previous file?

sorry, I think I'm confused.     

and herein lies my problem.

They show up in the job list one right after another same file name.

[David]

damn, you must be some kinda magician, or an evil sorcerer, whichever comes first.

so the only difference is the modification date, which is not part of the name?

weird...

It has to be adding some character to the name to keep it from overwriting, maybe an invisible one?
Can you get properties on both and see if there is a difference?

[G_Town]

Ok to hell with the previous question. My new Prinect question is....When the CIP file is processed it goes into the job name column but not the job number column so when the pressroom goes to call it up all the files have a job number of 1 which means that can't archive the setting and the supers cant print out the ink settings for the run which the customer requires.

We can manually go into Prinect select the job name and copy and paste it into the job number then it shows up fine at press but naturally prefer it populates the job number field automatically.

Ok shoot!

[gnubler]

Ok shoot!

Okay.

[Farabomb]

Ok to hell with the previous question. My new Prinect question is....When the CIP file is processed it goes into the job name column but not the job number column so when the pressroom goes to call it up all the files have a job number of 1 which means that can't archive the setting and the supers cant print out the ink settings for the run which the customer requires.

We can manually go into Prinect select the job name and copy and paste it into the job number then it shows up fine at press but naturally prefer it populates the job number field automatically.

Ok shoot!

You're the dude with a gun.

[G_Town]

Ok to hell with the previous question. My new Prinect question is....When the CIP file is processed it goes into the job name column but not the job number column so when the pressroom goes to call it up all the files have a job number of 1 which means that can't archive the setting and the supers cant print out the ink settings for the run which the customer requires.

We can manually go into Prinect select the job name and copy and paste it into the job number then it shows up fine at press but naturally prefer it populates the job number field automatically.

Ok shoot!

You're the dude with a gun.

and if I don't get an answer soon I'm going to whip it out. :angry:

Do ya feel lucky?

Well do ya PUNK!?!

[Farabomb]

<Cleavon Little> 'Scuse me while I whip this out. </Cleavon Little>

[David]

Ok to hell with the previous question. My new Prinect question is....When the CIP file is processed it goes into the job name column but not the job number column so when the pressroom goes to call it up all the files have a job number of 1 which means that can't archive the setting and the supers cant print out the ink settings for the run which the customer requires.

We can manually go into Prinect select the job name and copy and paste it into the job number then it shows up fine at press but naturally prefer it populates the job number field automatically.

Ok shoot!

We have a CIP application that is responsible for naming and setting the file output path here with our Esko workflow.
Does yours have a naming restriction or some other setting that is causing it to rename it to the name instead of the number?
Ours goes over with the entire file name (job no., underscore, job name, underscore, sig no.) like this 57999_joesprintjob_s3.

[G_Town]

Ok to hell with the previous question. My new Prinect question is....When the CIP file is processed it goes into the job name column but not the job number column so when the pressroom goes to call it up all the files have a job number of 1 which means that can't archive the setting and the supers cant print out the ink settings for the run which the customer requires.

We can manually go into Prinect select the job name and copy and paste it into the job number then it shows up fine at press but naturally prefer it populates the job number field automatically.

Ok shoot!

We have a CIP application that is responsible for naming and setting the file output path here with our Esko workflow.
Does yours have a naming restriction or some other setting that is causing it to rename it to the name instead of the number?
Ours goes over with the entire file name (job no., underscore, job name, underscore, sig no.) like this 57999_joesprintjob_s3.

Nope it lands in the job name area with the correct job number but in order for the pressroom to see it out at the press console you have to manually copy and past it into the job number field.

[David]

you got some weird chit there, have you spoke with the Kodak people about your config?

[G_Town]

Kodak? Shouldn't I be talking to the nice folks in der Lederhosen?

[gnubler]

Ja, was willst Du dann? Ich bin hier...