Error linking a DBF in Access

[Syndicate_Admin]

Good!
I'm having a very big problem linking .dbf files in Microsoft Access:
At the beginning of the year everything was going correctly, we used a very old CRM which uses these files that contain the information of the application. We had several computers that were linked through Access to them in order to generate reports or other processes (all reading). One day from only one of the machines tried to update the CRM to a newer version, but from that moment the other machines could no longer be linked to the DBF (of the oldest version of the software), appearing the error detailed in the image. I restored the machine to an earlier point, deeply uninstall the most modern CRM and nothing. No other machine could make the link, except one, a machine of not very high resources, which has the same office package (2010) as the others and the same version of Windows can access all the tables without any inconvenience.
Researching this later I realized that if I delete the . MDX some bases can be imported without problems (except the heaviest ones that give the following error: Error reserved (-1038); there is no message for this error). I installed the CRM on my home machine with some of the bases and tried to do the linking from my Access (from the office 365 package) and I also received the error: "System resources were exceeded". Similarly that error exists as long as the mdx is present.
I wanted to know if the error is due to some dll or some type of file that has been damaged, or if there is some way to link from odbc, which I tried and I have not had success either.
Thanks a lot!
Error image:

[Syndicate_Admin]

I tried to copy the same dll of the odbc of the machine that walks, install older ones and nothing. I did an indexing again from the application that allows you to recreate the index files. But the error persists.

The machine on which it works has 8GB of RAM, while in one of those that I am not being able to has a 9gen i7 and 32 GB of RAM and I can not

[AmiraBedh]

I am sorry for that ! Try to reach the support for the CRM.

[AmiraBedh]

I think that the upgrade of the CRM might have updated or modified the .DBF ODBC or OLEDB drivers. This might lead to an incompatibility with the older .dbf format or even conflicts with Access.
Make sure you have the latest ODBC or OLEDB drivers for .DBF files.
If possible, try installing older drivers on one of the machines and test linking.

.MDX files are index files associated with .DBF files. Sometimes, if there is corruption or if there's a version mismatch, it can cause issues.
As you mentioned, deleting the .MDX file allowed you to link some tables. This suggests some form of corruption or incompatibility with the index files.
Consider regenerating the index (if your CRM allows it) or avoid using them if possible.

The error also maybe related to memory-intensive usage. It's possible the structure or the size of the DBF file, especially when combined with indexing, is causing a resource constraint.
Try to ncrease the machine's RAM or resources, if possible..