Avatar of Eileen Murphy
Eileen Murphy
Flag for United States of America asked on

SQL View through ODBC to Access front-end after table change

Capture.JPG < Screenshot ------ Made a change to a SQL table this weekend -- and a SQL view linked through ODBC to an Access front-end went haywire. I've made table changes tons of times and never had this happen before. Needless to say ODBC rejected this as some of the fields were bit fields trying to be populated with dates... Ugh... Anyone see this before? I just recreated the view and all is right with the world...


* ODBCMicrosoft AccessMicrosoft SQL Server

Avatar of undefined
Last Comment
Eileen Murphy

8/22/2022 - Mon
ASKER CERTIFIED SOLUTION
Dale Fye

Log in or sign up to see answer
Become an EE member today7-DAY FREE TRIAL
Members can start a 7-Day Free trial then enjoy unlimited access to the platform
Sign up - Free for 7 days
or
Learn why we charge membership fees
We get it - no one likes a content blocker. Take one extra minute and find out why we block content.
Not exactly the question you had in mind?
Sign up for an EE membership and get your own personalized solution. With an EE membership, you can ask unlimited troubleshooting, research, or opinion questions.
ask a question
Eileen Murphy

ASKER
Hey Dale - This particular table is used universally throughout the application -- which is so weird because I've added fields before -- I refresh the views and tables (in SQL) and then refresh/relink them from the Access side... There are dozens and dozens of linked views - different tables - etc... and I never saw this where the fields get moved up but the field names don't -- so Access gets confused etc. 

Maybe I missed one this time -- this was new for me. Thank you so much for your input!!!
All of life is about relationships, and EE has made a viirtual community a real community. It lifts everyone's boat
William Peck