Error - 2147467259
Contents |
be down. Please try the request again. Your cache administrator is webmaster. Generated Sat, 08 Oct 2016 14:50:13 GMT by s_ac5 (squid/3.5.20)
If this is your first visit, be sure to check out the FAQ by clicking the link above. You may have to register before you can post: click the http://www.vbforums.com/showthread.php?665459-RESOLVED-run-time-error-2147467259(80004005) register link above to proceed. To start viewing messages, select the forum that you want to visit from the selection below. Results 1 to 10 of 10 Thread: [RESOLVED] run time error http://www.sql-server-performance.com/forum/threads/run-time-error-2147467259-80004005.34065/ '2147467259(80004005) Tweet Thread Tools Show Printable Version Subscribe to this Thread… Display Linear Mode Switch to Hybrid Mode Switch to Threaded Mode Nov 18th, 2011,09:51 PM #1 fkwinna View Profile View Forum Posts error 2147467259 Thread Starter Member Join Date Jun 2009 Posts 47 [RESOLVED] run time error '2147467259(80004005) I have the following error message run time error '2147467259(80004005) could not find installable ISAM when I running the following code Private Sub Form_Load() Dim s As String Dim rsitem As New ADODB.Recordset s = "provider =microsoft.jet.OLEDB.4.0;”" DB.ConnectionString = s = s & "data source=\" & App.Path & "\InventoryControl1.mdb\" DB.Open End Sub error - 2147467259 kindly try to help me Thank's for all fkwinna Reply With Quote Nov 18th, 2011,10:25 PM #2 Doogle View Profile View Forum Posts PowerPoster Join Date Jul 2006 Location Maldon, Essex. UK Posts 6,334 Re: run time error '2147467259(80004005) I think your Connection String should be: Code: DB.ConnectionString = s & "data source=" & App.Path & "\InventoryControl1.mdb" you also need to establish DB as an ADODB.Connection eg Code: Dim DB As ADODB.Connection Set DB = New ADODB.Connection Reply With Quote Nov 18th, 2011,10:33 PM #3 fkwinna View Profile View Forum Posts Thread Starter Member Join Date Jun 2009 Posts 47 Re: run time error '2147467259(80004005) Dear Doogle Thank you for your urgent reply,But I'm sorry , the problem still I tried your statement but I get the same error, I think that the error at MSACCESS2000 I tried to repaire it or reinstall but nothing happen Reply With Quote Nov 18th, 2011,10:56 PM #4 Doogle View Profile View Forum Posts PowerPoster Join Date Jul 2006 Location Maldon, Essex. UK Posts 6,334 Re: run time error '2147467259(80004005) Can you copy and paste your actual code please. There seems to be a typo in your Provider str
by khayam, May 8, 2013. khayam New Member heloo dear .. i am facing this error from last 4 days ...... please give me solution . Run-time error "-2147467259 (80004005): [Microsoft][ODBC Driver Manager]Data source name not found and no default driver specified khayamshah52@yahoo.com ONE Shah khayam, May 8, 2013 #1 davidfarr Member It does not look like an error that one would see in SQL Server Management studio. Are you seeing this error from a program application or a website ? ..perhaps one written in ASP or a .NET programming language ? Have you (or the programmers) checked the "connection string" (the line of programming code) that is being used to access the database ? Does the database and SQL Server instance still exist and is the service running ? Also check here for some possible answers; http://support.microsoft.com/kb/306345 davidfarr, May 8, 2013 #2 khayam New Member we install 4 types of s/w like Sql server 2000, crystal reports, accounting (cranium) software, and sharidns widgets... after that i make odbc connection , odbc connection is successfully create ... but after when i run my application exe above error was occurred – khayam, May 8, 2013 #3 davidfarr Member How exactly are you "making an ODBC connection" ? You are probably using a System DSN or User DSN connection, is that correct ? When you configure a ODBC DSN there is a button you can press to "Test Data Source". Does that test succeed ? The first thing to do is to make sure that your database is available and that the SQL Server service is running. Can you connect to the SQL server database using client tools such as SQL Server Management Studio, or Query Analyzer, or Enterprise Manager ? If you cannot connect using standard client tools such as these, then your problem is on the SQL Server and you will need to investigate any errors that you get from that. If you can connect successfully to the database using these client tools mentioned above then your problem is probably with the DSN connection settings used by the other applications. Are you referencing the correct server name, correct username and password in the ODBC DSN ? Are you using Windows Authentication or SQL Server Authentication in the ODBC DSN configuration ? Does that authenticated user (Windows or SQL Server) have a valid login and valid permissions on the SQL Server instance ? If you have checked all those things and if you are sure that your database credentials are co