Therefore the need to try an correct the problem by installing a more current version of MDAC, and/or changing the reference for ADO DB to a valid one, or checking the connection string for a syntax error.
Simply put it, it is like a "File not found" (the ISAM driver for the version specified) or "Registry entry not found" (again, the ISAM driver entry for the version specified) error. Nor has it been determined if the DB even exists, or the path is correct or not. This could be because of one of the two mentioned possibilities, or, more often, a syntax error in the connection string which is causing the problem.Īt that point, an actual connection to the db hasn't even been attempted yet, so whether a password is needed or not hasn't even been determined yet. The error means that the driver specifications, or the driver, for the provider given in the connection string is not found on the clients machine.
>".often occurs on Access databases with passwords."Īnd seriously doubt that that will cause it on an MDB. If this post contains any suggestions for the use or distribution of code, components or files of any sort, it is still your responsibility to assure that you have the proper license and distribution rights to do so! RE: Could Not Find installable ISAM CodeFish (Programmer) 1 Oct 02 10:13 If one of the latter two, then search in your code for a ConnectionString and post it here). If the error still happens, then post here how you are connecting to the Database (Adodc1 - A data control, ADO code or a ADO class. If you are using a Jet MDB then 2.5 should be sufficient.Ĭhange the reference to the correct version of ADO (under the menu point: PROJECT|REFERENCES if the version of "Microsoft ActiveX Data Objects Library" is not 2.5 or higher (maybe 2.0) then deselect the one checked, and select the 2.5 Version. And, as I stated, download and install MDAC 2.5 or higher. Make sure you have the most recent VB6 service pack (SP5 from )Ģ.
0 kommentar(er)
