Run Time Error 2147467259 80004005
  Home FAQ Contact Sign in
 
Advanced search
MATCHING GROUPS



more...
POPULAR GROUPS

more...

found 130 articles for 1.958 sec
I am connecting from an Access front end to a SQL Server 2005 Express database on a remote PC. I have enabled TCP/IP on the server and turned off firewalls on both boxes. The first recrodset opens and reads the data fine. The subsequent one (which runs after it gives the following error on update. Run-time error "-2147467259 (80004005): [Microsoft][ODBC SQL Server Driver][SQL Server]Could     

Group: microsoft.public.access.formscoding · Group Profile · Search for Run Time Error 2147467259 80004005 in microsoft.public.access.formscoding
Author: Dave
Date: Apr 26, 2007 10:16

"Chace" <Chace@discussions.microsoft.com> wrote in message <2627DD3D-35DC-464D-8DCC-95ED3EE3CDBF@microsoft.com>: Thanks for your help Roy-Vidar. I tried giving unique names to the three recordsets but the connection error still occurred. However, through more troubleshooting, I found the problem and fixed it. The Access database that I connect to contains many linked tables to
Show full article (1.22Kb)
Thanks for your help Roy-Vidar. I tried giving unique names to the three recordsets but the connection error still occurred. However, through more troubleshooting, I found the problem and fixed it. The Access database that I connect to contains many linked tables to my company's ERP system (another database). A long time ago, when I created these links, I found that I was not conistent     

Group: microsoft.public.access.modulesdaovba · Group Profile · Search for Run Time Error 2147467259 80004005 in microsoft.public.access.modulesdaovba
Author: RoyVidar
Date: Feb 21, 2007 10:53

"Chace" <Chace@discussions.microsoft.com> wrote in message <AF4D8EE3-51A5-492B-88C8-C4729077E798@microsoft.com>: I have a weird problem: I get a connection run-time error if I try to open the third recordset in the procedure below. Does anyone know what the problem might be? Private Sub cmd_Update_Click() Dim cnn As ADODB.Connection Dim rs As ADODB.Recordset Dim
Show full article (5.00Kb)
I have a weird problem: I get a connection run-time error if I try to open the third recordset in the procedure below. Does anyone know what the problem might be? Private Sub cmd_Update_Click() Dim cnn As ADODB.Connection Dim rs As ADODB.Recordset Dim MySQL As String Dim dtStart As Date Dim dtEnd As Date Dim strMonth As String Set rs = New ADODB.Recordset Set cnn = New ADODB     

Group: microsoft.public.access.modulesdaovba · Group Profile · Search for Run Time Error 2147467259 80004005 in microsoft.public.access.modulesdaovba
Author: Chace
Date: Feb 21, 2007 10:50

Dean Thanks for getting back -- HTH Nick Hodge Microsoft MVP - Excel Southampton, England nick_hodgeTAKETHISOUT@zen.co.uk.ANDTHIS www.nickhodge.co.uk "DeanH" <DeanH@discussions.microsoft.com> wrote in message news:5B3D1410-2436-44DB-AEFD-1365423A723A@microsoft.com... Many thanks for your reply, Nick. I have made a note of your suggestion for the future. Just as you
Show full article (4.75Kb)
Many thanks for your reply, Nick. I have made a note of your suggestion for the future. Just as you were writing your reply, I found the problem. There was mysterious Toolbar on the Customize Toolbars listing, the toolbar itself being blank. This obviously was left behind after the macro, from the file I previously mentioned, did not clean up behind itself. When this toolbar was deleted,     

Group: microsoft.public.access.modulesdaovba · Group Profile · Search for Run Time Error 2147467259 80004005 in microsoft.public.access.modulesdaovba
Author: RoyVidar
Date: Feb 21, 2007 08:40

Dean Try opening Add-ins... and uncheck all the add-ins, close and re-start Excel. If this works, add them back until the error re-appears, re-starting each time you add one back. If this isn't the case, try looking in xlStart and see if there is anything there. (You should only have personal.xls, book.xlt and sheet.xlt...OR nothing!). Move anything in here (don't delete it) and
Show full article (3.55Kb) · Show article thread
Thanks this now works. I had previously added it to the stop of the stored procedure but then noticed it was not in the SP code when modifying it and therefore added it to within the Alter statement. What difference does this one statement do to the returned data? On 19 Oct, 16:31, "Sylvain Lafontaine" <sylvain aei ca (fill the blanks, no spam please)> wrote: > Add the SET NOCOUNT ON     

Group: microsoft.public.access.modulesdaovba · Group Profile · Search for Run Time Error 2147467259 80004005 in microsoft.public.access.modulesdaovba
Author: Chace
Date: Feb 21, 2007 08:01

Show full article (2.68Kb)
    

Group: microsoft.public.excel.crashesgpfs · Group Profile · Search for Run Time Error 2147467259 80004005 in microsoft.public.excel.crashesgpfs
Author: Nick Hodge
Date: Aug 22, 2006 23:50

Show full article (2.56Kb) · Show article thread
    

Group: microsoft.public.excel.crashesgpfs · Group Profile · Search for Run Time Error 2147467259 80004005 in microsoft.public.excel.crashesgpfs
Author: DeanH
Date: Aug 22, 2006 23:27

Show full article (2.19Kb) · Show article thread
    

Group: microsoft.public.excel.crashesgpfs · Group Profile · Search for Run Time Error 2147467259 80004005 in microsoft.public.excel.crashesgpfs
Author: Nick Hodge
Date: Aug 22, 2006 13:16

Show full article (1.51Kb)
    

Group: microsoft.public.access · Group Profile · Search for Run Time Error 2147467259 80004005 in microsoft.public.access
Author: Fred Loh
Date: Apr 15, 2008 08:51

Show full article (0.29Kb)
    

Group: microsoft.public.access.adp.sqlserver · Group Profile · Search for Run Time Error 2147467259 80004005 in microsoft.public.access.adp.sqlserver
Author: Robin9876
Date: Oct 22, 2007 06:33

Show full article (6.30Kb) · Show article thread
1 · 2 · 3 · 4 · 5 · 6 · 7 · 8 · 9 · next