If you are using Excel 32 bit you need to use the 32 bit odbc divers.
If you are using Excel 64 bit you need to use the 64 bit odbc divers.
The operating system, doesn't really matter.
============================================================================================
When you add tables in MS Query, then there is initially no join between the two tables.
So for each record in the first table, every record in the second table will be shown and so on.
If you 2 tables with 1000 record each that is 1,000,000 record that will be returned. This will take a long time to do and so it may appear that MS Query has hung.
To prevent this you need to turn off the Auto Query button and only press query or return, after you have joined the tables.
Screenshot 2022-02-09 115400.jpg
If you have a lot of fields and a lot of records in your query and you are running it over a network it is going to be taking a long time to get all that data from the server and then filter it down to just what you want.
There have been a couple of bad fields in odbc in the past, memo fields that crash ODBC.
There are also some Pseudo tables that don't really exist, they are made up from other tables, so take ages to load.
The projects table links to lots of other tables so queries on it are exceptionally slow.
Diving deeper, if none of the above helps, then knowing what your query is would be useful alone with the number of records (Help About will give you that for the main tables).
If you open your query in MS Query and click on the SQL button, you can copy and paste that into a reply.
Finally, it is possible that there is a problem with your sage data files, backup, run check data, then reindex, compress and check data again.
You do not have the required permissions to view the files attached to this post.