VB6 ADO Crashing When Trying to Access SQL Server under Win XP

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?

Jan Hyde

Guest

n/a Posts

November 3rd, 2006
07:35 AM
#2

Re: VB6 ADO Crashing When Trying to Access SQL Server under Win XP

"David C. Barber" <david@NOSPAMdbarber.com>'s wild thoughts
were released on Thu, 2 Nov 2006 22:56:21 -0700 bearing the
following fruit:

Quote:

Originally Posted by

>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)

David C. Barber

Guest

n/a Posts

December 30th, 2006
05:25 AM
#3

Re: VB6 ADO Crashing When Trying to Access SQL Server under Win XP

"Jan Hyde" <StellaDrinker@REMOVE.ME.uboot.comwrote in message
news:up0mk21i46i6bqgdi7vt9ak7ji7h3nlkgk@4ax.com...

Quote:

Originally Posted by

"David C. Barber" <david@NOSPAMdbarber.com>'s wild thoughts
were released on Thu, 2 Nov 2006 22:56:21 -0700 bearing the
following fruit:
>

Quote:

Originally Posted by

I have a VB6 application that uses command line ADO to communicate to a

SQL

Quote:

Originally Posted by

Quote:

Originally Posted by

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

Quote:

Originally Posted by

Quote:

Originally Posted by

talk to different databases on this same SQL Server.

The problem is that, when I load the application on a Win XP SP2 computer

Quote:

Originally Posted by

Quote:

Originally Posted by

crashes during execution with an Invalid Object Name message

(-2147217865)

Quote:

Originally Posted by

Quote:

Originally Posted by

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

Quote:

Originally Posted by

Quote:

Originally Posted by

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

Quote:

Originally Posted by

Quote:

Originally Posted by

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.

Steve Gerrard

Guest

n/a Posts

December 30th, 2006
06:15 PM
#4

Re: VB6 ADO Crashing When Trying to Access SQL Server under Win XP

"David C. Barber" <david@NOSPAMdbarber.comwrote in message
news:5PGdnSC-vowDngvYnZ2dnUVZ_tmknZ2d@comcast.com...

Quote:

Originally Posted by

>
>
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.
>
>

If you want to send a post to both CLVB and CLBV, then cross-post, don't
multi-post.

Multi-post: Two separate posts are sent, each addressed to a single newsgroup,
but containing identical text.

Cross-post: A single post is sent, with two newsgroups listed in the address
field, separated by a comma, similar to sending an email to two people at once.

If you cross-post, then replies made in one newsgroup will also appear in the
other group, avoiding a lot of confusion, repetition, and annoyance. Also in
many newsreaders, if I read the post in one group, it is automatically marked as
read in the other group as well.