Greetings to the well of knowledge...
Not sure of where I should post this, so posting it here.
I recently upgraded my SQL Server back-end from 2008R2 to 2017. I am now trying to get my existing front-ends working using 2017.
I have encountered one issue. I have some code that executes a stored query using DoCmd.OpenQuery. Sometimes, but not always, this command throws Error 3265 generated by DAO.QueryDefs. I set a breakpoint just before this command and inspected the stored query to ensure that all fields are properly defined...all appear to be, and I can preview the results of the query.
Would this be some fallout from the migration from 2008R2 to 2017?
Thanks,
Ken
Not sure of where I should post this, so posting it here.
I recently upgraded my SQL Server back-end from 2008R2 to 2017. I am now trying to get my existing front-ends working using 2017.
I have encountered one issue. I have some code that executes a stored query using DoCmd.OpenQuery. Sometimes, but not always, this command throws Error 3265 generated by DAO.QueryDefs. I set a breakpoint just before this command and inspected the stored query to ensure that all fields are properly defined...all appear to be, and I can preview the results of the query.
Would this be some fallout from the migration from 2008R2 to 2017?
Thanks,
Ken
Last edited: