![]() In reference to the OLE DB Provider portion of your question, it appears to be a similar type of problem where the application is not able to locate the configuration for the specified provider. It may not be the same product brand that you have, however it is a generic problem that is encountered when using ODBC data source names. Here is an article that may provide some additional details One letter wrong is all it takes for a DSN to be mismatched. It's also important to make sure the spelling of the DSN matches that of the configured DSN in the ODBC Administrator. Then when the 32-bit application attempts to connect using that DSN, "Data source not found." occurs. You can change the paths by changing the values assigned to the global array named gsFiles. You should replace these default paths with the locations of files on your own server. Default file paths are provided in the sample. Where I see this tripping people up is when a user uses the default 64-bit ODBC Administrator to configure a DSN thinking it is for a 32-bit DSN. Starts downloading five files when the user clicks Download. If you need to use the 32-bit ODBC Administrator tool on a 64-bit Windows system, you will need to run the one found here: C:\Windows\SysWOW64\odbcad32.exe However, on a 64-bit Windows machine, the default is the 64-bit version. DirectShow DirectX Download Manager Driver Signing EventSystem m. On 32-bit and 64-bit Windows, the default ODBC Administrator tool is in c:\Windows\System32\odbcad32.exe. Testing the Microsoft Fax Printer Driver If modem or phone line problems don't seem. If these do not match, it is possible to configure a DSN for a 32-bit driver and when you attempt to use that DSN in a 64-bit application, the DSN won't be found because the registry holds DSN information in different places depending on ELF (32-bit versus 64-bit).īe sure you are using the correct ODBC Administrator tool. In other words, you need a 32-bit driver for a 32-bit application or a 64-bit driver for a 64-bit application. ![]() It is important that your ODBC driver's executable and linking format (ELF) is the same as your application. That error means that the Data Source Name (DSN) you are specifying in your connection configuration is not being found in the windows registry. In reference to the error: Data source name not found and no default driver specified.
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |