How to fix "Column Does Not Exist on Table Error" when the column does exist in the database schema - Developer Network Q&A

RE: How to fix "Column Does Not Exist on Table Error" when the column does exist in the database schema

Andrew Brits — Mon, 17 Feb 2025 19:13:07 +0000

@jcourter You need only touch the file itself to update the last modified date on the file - so opening it up in a text editor, adding a space, removing the space and saving (for example) will do the trick.

Answer to: How to fix "Column Does Not Exist on Table Error" when the column does exist in the database schema

jcourter — Fri, 31 Jan 2025 17:47:55 +0000

This can happen if the DAO object wasn't regenerated after the attribute was added. This means the database was updated to include the column, but the DAO object did not get created.

The solution to solve the issue is to make a change to your model, in this example HPEC.Book, then build the module. Because we have edited the model, when you next build the module, it will generate a new DAO object, which should solve the issue.

How to fix "Column Does Not Exist on Table Error" when the column does exist in the database schema

jcourter — Fri, 31 Jan 2025 17:45:55 +0000

I am currently trying to insert a record into a model and am receiving the error "Column does not exist on table". I have checked the database schema and in this example, the column "TITLE" does exist within the HPEC_BOOK table. Why am I receiving this error even though the column exists?

I have also tried building the module and it has not fixed the issue.

776