I am stumped.?ÿ Import a job file, it throws out this error.?ÿ So import the FXL, error still there, will not process feature codes because it won't recognize the file that I imported is an FXL, I guess, who knows what is upsetting it.
Tried opening and saving using latest Feature Code Processing manager, nope, not it.
Instead of drag and drop tried using the manual import routine, nope.
Only thing technical support can figure out is there are feature codes in the job file which aren't in the FXL but THAT ALWAYS HAPPENS. You know Access THEIR software does that when you stake out a point, the code is the point name of the point you staked out.?ÿ Sometimes the feature isn't on the list.?ÿ Try not to have 6000 codes in there.
If anyone has any idea what the secret handshake might be to make TBC recognize its own file format I would appreciate knowing it.
It doesn't exist but it does exist, weird.
Have you tried changing the name of the .FXL? I have in the past seen TBC get upset if there is a character in the name or if the name is too long. You have it set with the same feature definition file?
I've seen this before as well.
Can you import the .jxl instead of the .job? I would try that.
There is a "-" in the name, maybe that's it.
I made the file using the Feature Definition Manager and put it on the Controllers where it works fine.
I will try a new name.
Okay, tried renaming the file and did a small test project.
Still throwing the yellow flag.
No idea what is going on.
Support is trying to figure it out.
Figured it out with the help of Robert at California Surveying and Drafting...
The secret handshake is...
put the JOB file and the FXL in the same folder then drag and drop them together into TBC.?ÿ That works and it processes feature codes.
I don't know how to fix it in old projects but don't need to right now.?ÿ Next topo it will be good to know how to use it.
More...
apparently the FXL only has to be in the same folder with the JOB file. Each new JOB imports the FXL again. TBC throws a message about undoing all previous feature code processing, say yes to that. All the imported JOBs will stay associated with the one FXL. It??s very picky about how you do it.
