We have recently tried to set up a 'new' (Win95 OSR2) computer with Max5 but get the above ODBC driver error. In Control panel ODBC driver utility the driver is shown as installed but there's no entry in System DSN and if you try to add one it just doesn't succeed.
We've tried re-installing and a few other things but with no success. We use Max5 on a Novell 3.12 network with Client32 with no problems, but need the ODBC drivers (they work and install on our other computers).
The only other noticeable thing is that Max assumes 'ownership' of .mde files, we have to modify that to allow MS Access to use them again.
Any ideas/help appreciated?

Am I right in thinking that the error is right at the end of the install proceedure?

If so this could be due to a file named MSVCRT40.DLL that may be corrupted. You can get a new copy from the root of a Microsoft Office 97 CD

If may also be worth re-running the ODBCADMIN install kit which you'll find on the Max5 CD in the Files\ODBC folder.

We have had some funny problems like this they can be due to file version inconsistencies amongst the files that provide the ODBC services.

I hope this helps.

Ian Wallace
Newbury, UK

Thanks for suggestion Ian, the error is at the end of the installation process. We've tried both ideas and also copied across the max ODBC driver dll from another computer.

The problem is easy to demonstrate - if you go into Control Panel, ODBC Data Sources (32 bit) and try to add an entry to the User, System or File DSN tabs (selecting the Max ODBC driver of course) it goes thro' the motions but never offers the options tailored to maximizer requirements and never actually adds an entry.
Of course the Drivers tab displays all available drivers including the Maximizer one.
Any ideas?

As mentioned above I think this is due to file versions but I'm afraid I'cant be more specific. Sorry.

Ian