Hmmm...
IMHO, logical places to enter image links for routings would be:
RO-A. - Select or enter a sequence #, have an entry somewhere along the standard flow that allows you to do a quick file name entry, checkbox for 'global link path', and 'T' or 'L', [thumb or link]. I write my routings in a very systematic way, trying to do a very detailed step-by-step instruction set and would make sense to me for the link entry to be here, so as I'm writing my initial master routing I can easily keep things in check and not lose my place instead of having to enter all the instructions, then go back to a separate data entry sheet to link all my files. On that note, I write all my sequences in intervals of 10, and would appreciate if I happen to rename sequence 30 to sequence 40 that the link intelligently follow along...
WO-A. Why? - In the event you have to make a one time change to a routing that has already been converted to 'F'. Similar to the interface of WO-K-A.. wait, scratch that, WO-K-A is horrible.. but you get my drift. It might also be prudent to have it block change requests to 'R' work orders since they should already be 'Live and in production".
IN-A. Why? - It's probably the default starting place for most folks when they are looking for general information. At the least this could be a link to the same screen used in one of the above suggestions of not a separate entry form.
Oh, and BTW, while I understand what you suggested in your last post, it is still not properly printing on the default ENWOC3.RTM. Using IN-A to drill to the routing seems to be on the right path because it informs me I'm editing the link for P35-1206 - 40 [item # and sequence #]. At this stage my preview also displays correct. I'm linking a jpg file, its tagged as 'traveler', 'thumbnail' and 'parent'. Its also set up using our global path.
Oh, and on a possibly unrelated note, since the update to 12/21/08, none of my .pdf files link with the travelers when they print. I have to manually open the link through IN-A and print.

This seems like some simple problem I've overlooked which is adding to my frustration. Happy Monday!

And as always, I appreciate the help and input of my fellow forum users. We are such a diverse crowd with many backgrounds and specialties whom all seek a unified solution to our database problems.
-Mike