The very phrase you quote--from the message in the application.log--does indeed show "additional info", at least in that you'd not shown previously the error message saying, "Could not find QUERY [jobs]". And the exception log indicates the same error.
So help us out: had you seen that before and not told us? Or did you miss it being in what you've just posted? Either is OK. Just help us understand.
More to the point, if you may feel it "doesn't tell me anything meaningful ", then I'll share first that I see now how that example code (from the Adobe docs) happened to use a cfquery called "getJobData" but then referred in the cfindex to "jobs". That seems a mistake, easily corrected by them or you: did you perhaps just use that EXACT code, changing only the datasource value and sql statement? If so, then just change either that cfquery name value or the cfoutput query value, so that they match.
Second, if you may respond with more questions, it may help for you to clarify something: are you perhaps the owner of this web site (with this code from cf 4.51, from 25 years ago), who is not really a developer otherwise? And are you perhaps "just needing to get this web site running on a modem cf version", for whatever reasons? If all that's true, knowing it may better help us in guiding you. We do tend to get questions here from developers rather than others, and we may leave out details or presume something's more apparent than maybe it woukd be for someone in that situation.
But maybe the suggestions before that question will get you over this hump and you'll be all set.
To answer your first question, I'd seen the "Could not find QUERY [jobs]" a number of times as I was trying to perfect the code as it was choking on earlier lines in the code as I worked my way through getting it correct and thought it was a generic message of little consequence. I apologize for my ignorance.
The example in adobe docs was [query="getCourses"]. I had originally changed it to "getJobData" and then changed it to "jobs" because our current cfindex code scheme in 4.51 uses "jobs". Of course, I am trying to keep as much of the nomenclature in 2023 the same as that used 4.51 in possible.
To answer your next question, yes I own the website. As I believe I mentioned in a previous thread, the 4.51 development was done by a young man I placed as a CF developer who was touted by his boss as a "whiz kid" after he worked for him for a couple of years. The "whiz kid" did the inital 4.51 coding for us as a side job and his work was exceptional. Given the size of our system, we only found 3 bugs in it after pounding on it for a full year.
As to myself, a long, long time ago, in a different universe I did a fair mount of COBOL programming on a Series 1 IBM mini-computer. Bottom line, I learned enough about syntax & logic to be able to handle "maintenance programming" on our 4.51 system. I could read the "whiz kids" code well enough to modify it as needed without issue. Bottom, bottom line writing new CF code from scratch is a challenge. I can learn it, but it requires a fair amount of time & effort.
With all that said, your last suggestion concerning the code did the trick. Changing the input & output query names to match (jobs); commenting out the "custom1" field solved my problem. I now have a collection with 5500+ documents in it. Thanks for your patience & help Charlie. Apparently, "old dogs can learn new tricks.
For anyone who stumbles across this thread who needs a template from which to create a collection from a database table, this one worked.
**************************
<!---EXAMPLE #3: Index a QUERY (type = "custom") using custom1. ------------>
<!--- Retrieve data from the table. --->
<cfquery name="jobs" datasource="TEN">
select * from tblJobOrders
</cfquery>
<!--- Update the collection with the above query results. --->
<!--- key is JobOrderNum in the tblJobOrders table. ---->
<!--- body specifies the columns to be indexed for searching. --->
<cfindex
query="jobs"
collection="TPI_Jobs"
action="Update"
type="Custom"
key="JobOrderNum"
title="title"
body="JobOrderNum,JobTitle,JobReq1,JobReq2,JobReq3,JobReq4,JobPref1,JobPref2,JobPref3,JobPref4,JobReqNotes"
>
<h2>Indexing Complete</h2>
***************************************
AdChoices