2 min readfrom Microsoft Excel | Help & Support with your Formula, Macro, and VBA problems | A Reddit Community

Excel Crashes w/ ODBC Query After Copilot Integration

Our take

Since the recent forced integration of Copilot in Excel (Version 2604, Build 19929.20136), many users have experienced crashes while refreshing ODBC queries linked to their ERP databases. With extensive SQL experience, I can confirm that the queries themselves are sound, and the issue seems directly tied to this update, as machines without it function correctly. Unfortunately, our IT department has found no option to remove Copilot locally or manage it via the Office 365 Admin portal.

The recent reports of Excel crashing due to the integration of Copilot have highlighted a significant challenge many businesses face when adopting new technology. As organizations increasingly rely on data management tools, ensuring stability and compatibility with existing systems is paramount. The situation described by users struggling with ODBC queries and ERP database connections after the Copilot update raises important questions about the balance between innovation and reliability in software updates. This incident serves as a reminder of the potential pitfalls associated with rapid technological advancements, especially within established platforms like Excel.

The frustration expressed by users who have utilized these queries for years is understandable. With a wealth of experience in SQL and a deep familiarity with their databases, they rightly expect updates to enhance their workflows, not hinder them. This situation echoes broader industry concerns about the pace of innovation, as seen in our article, I Let CodeSpeak Take Over My Repository, which discusses the challenges of transitioning to AI-native workflows. Users are often caught in the crossfire between the allure of new features and the stability of their existing processes.

Moreover, the inability to disable the Copilot feature or manage it through the Office 365 Admin portal further exacerbates the issue. This lack of control over software updates can lead to decreased productivity and operational disruptions. It raises a critical question: how can companies ensure that their tools serve them effectively, especially when new features are introduced? This incident emphasizes the need for organizations to adopt a more strategic approach to technology integration, prioritizing user feedback and the practical implications of updates. For many businesses, this means advocating for a more transparent update process that allows for user testing and feedback before widespread implementation.

As organizations grapple with these challenges, the industry must also consider the implications for future software development. The push towards more integrated AI capabilities, such as those seen with Copilot, should not come at the expense of user experience and system stability. As we look to the future, it is essential for tech companies to strike a balance between innovation and reliability. This balance is crucial for fostering user trust and ensuring that technological advancements truly empower users rather than hinder their progress.

In conclusion, the recent Copilot integration issues in Excel serve as a cautionary tale for both users and developers. As businesses navigate this evolving landscape, they must advocate for solutions that prioritize usability and stability. Looking ahead, it will be interesting to see how software developers respond to these challenges and whether they will adopt a more user-centric approach in their future innovations. How can organizations ensure that the drive for innovation does not compromise the reliability of the tools they depend on daily? This is a question worth watching in the coming months as the industry seeks to adapt to its increasingly complex technological environment.

Ever since this was forcefully installed the other week, all our files with ODBC connections to our ERP database are crashing when refreshing. My entire company has been using these queries for years, this all started when this update rolled out. I've been writing SQL for 20 years, I know our database, I created these files, there's nothing wrong with the queries and nothings been depreciated/legacy from the recent update from our understanding.

We confirmed the recent forceful Copilot integration is likely causing the issue, Version 2604 (Build 19929.20136). A machine which did not have the update has no issues with the files or query refresh. We then installed the update, replicated the problem. There's been no change to our server environment either.

Our IT Department can't remove Copilot from Excel, there's no option locally on the users machine or a specific license to manage for tenants on the Office 365 Admin portal. Anyone with a working solution for Office 365 Business would be greatly appreciated.

DOA Solutions Thusfar:

  • Uncheck "Turn on optional connected experiences" from File > Account > Account Privacy > Manage Settings
  • File > Options > Copilot (does not exist)
  • Office 365 Admin Portal remove license (does not exist)

https://preview.redd.it/ny5qxsdzl41h1.jpg?width=454&format=pjpg&auto=webp&s=9d2a949909ab7dcdafc99ce73dff7d8ddc8c88c4

submitted by /u/RevanOn3r
[link] [comments]

Read on the original site

Open the publisher's page for the full experience

View original article

Tagged with

#Excel alternatives for data analysis#natural language processing for spreadsheets#generative AI for data analysis#financial modeling with spreadsheets#Excel compatibility#Excel alternatives#machine learning in spreadsheet applications#rows.com#spreadsheet API integration#enterprise-level spreadsheet solutions#business intelligence tools#AI-driven spreadsheet solutions#no-code spreadsheet solutions#data cleaning solutions#Excel#Copilot#ODBC#Office 365#ERP database#query refresh