home bbs files messages ]

Forums before death by AOL, social media and spammers... "We can't have nice things"

   comp.lang.visual.basic      MS Visual Basic discussions, NOT dot-net      10,840 messages   

[   << oldest   |   < older   |   list   |   newer >   |   newest >>   ]

   Message 10,333 of 10,840   
   David C. Barber to Jan Hyde   
   Re: VB6 ADO Crashing When Trying to Acce   
   29 Dec 06 23:16:10   
   
   From: david@NOSPAMdbarber.com   
      
   "Jan Hyde"  wrote in message   
   news:up0mk21i46i6bqgdi7vt9ak7ji7h3nlkgk@4ax.com...   
   > "David C. Barber" 's wild thoughts   
   > were released on Thu, 2 Nov 2006 22:56:21 -0700 bearing the   
   > following fruit:   
   >   
   > >I have a VB6 application that uses command line ADO to communicate to a   
   SQL   
   > >Server database.  I developed it under Visual Studio 6 SP 6 on a Win 2K   
   > >machine, and it is very similar to other applications I've also developed   
   to   
   > >talk to different databases on this same SQL Server.   
   > >   
   > >The problem is that, when I load the application on a Win XP SP2 computer   
   it   
   > >crashes during execution with an Invalid Object Name message   
   (-2147217865)   
   > >on the second or third database recordset Open.  The invalid object   
   > >referenced is a table name in SQL Server.  Other, similar, applications   
   > >built from the same code-base don't crash.  And everything runs fine   
   under   
   > >Win 2K.  It also runs fine in the IDE on 2K and XP.   
   > >   
   > >I'm building the install package using the Package & Deployment Wizard,   
   > >which has never screwed me up before.  And regardless of whether I build   
   the   
   > >setup package on XP or 2K, the .exe still crashes on XP.   
   > >   
   > >Any suggestions?   
   >   
   > Don't mulipost for one...   
   >   
   > Jan Hyde (VB MVP)   
   >   
   > --   
   > Migration: A headache birds get when they fly down for the winter.   
   > (Richard Lederer)   
   >   
      
   I'll quit multi-posting when CLVB and CLBV are combined into one group.   
   Until then, there's no good indication which group is better to be using at   
   a given time.  It's stupid to have both groups, and we'd be better off with   
   only one of them.   
      
   --- SoupGate-Win32 v1.05   
    * Origin: you cannot sedate... all the things you hate (1:229/2)   

[   << oldest   |   < older   |   list   |   newer >   |   newest >>   ]


(c) 1994,  bbs@darkrealms.ca