Type Name is Invalid error -- Windows 2000/98 application with SQL Server/stored procedure problem 
Author Message
 Type Name is Invalid error -- Windows 2000/98 application with SQL Server/stored procedure problem

You should always install the version that is on your development machine or higher when you deploy an application. No matter what yuo have
set in the Project References.

Scot Rose, MCSD
Microsoft Visual Basic Developer Support

Want to know more? Check out the MSDN at msdn.microsoft.com or the Microsoft Knowledge Base at support.microsoft.com

This posting is provided AS IS, with no warranties, and confers no rights.

--------------------

Quote:


>Newsgroups: microsoft.public.sqlserver,microsoft.public.vb,microsoft.public.vb.database,microsoft.public.vb.general

>Subject: Re: Type Name is Invalid error -- Windows 2000/98 application with SQL Server/stored procedure problem
>Lines: 71
>X-Priority: 3
>X-MSMail-Priority: Normal
>X-Newsreader: Microsoft Outlook Express 6.00.2600.0000
>X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2600.0000


>X-Abuse-Info: Please be sure to forward a copy of ALL headers
>X-Abuse-Info: Otherwise we will be unable to process your complaint properly.
>NNTP-Posting-Date: Tue, 13 Aug 2002 16:50:42 EDT
>Organization: WEBUSENET.com
>Date: Tue, 13 Aug 2002 17:04:17 -0400
>Path: cpmsftngxa06!tkmsftngp01!newsfeed00.sul.t-online.de!t-online.de!fr.usenet-edu.net!usenet-edu.net!fr.clara.net!heighliner.fr.clara.net!

news-hub.siol.net!newsfeeds-atl2!news.webusenet.com!pc01.webusenet.com!e3500-atl1.usenetserver.com.POSTED!not-for-mail

- Show quoted text -

Quote:
>Xref: cpmsftngxa06 microsoft.public.vb.database:85331
>X-Tomcat-NG: microsoft.public.vb.database

>Guess what? The problem has been resolved, but just fyi for ppl who are
>having the same problem -- the problem was resolved by installing MDAC
>2.6... the version prior was ver. 2.5.

>Cheers!
>--husky



>> Oops... the error should read (typo here) ...
>> "run-time error '-2147217872(80040e30)': type name is invalid."

>> -- husky



>> > Hello,

>> > I am developing an application in Visual Basic 6 that uses a back-end
>SQL
>> > Server 2000 database with stored procedures. This application will be
>used
>> > on Windows 2000 and Windows 98.

>> > The application is close to completion and is currently in test/debug
>when
>> I
>> > came across this error while testing on Win98 (no errors occur in
>> Win2000):
>> >  "run-time error '-2147217872(80040e30)': type name is envalid." This
>> error
>> > occurs in the Command.Parameters.Append CreateParameter line

>> > For example:
>> > =========
>> > dim oCmd as ADODB.Command
>> > set oCmd = New ADODB.Command

>> > with oCmd

>> > <!--- ERROR HERE

>> > mOrder.StockAmount) <!--- ERROR HERE
>> >  .activeconnection = oConn
>> >  .commandtext = "sp_myStoredProc"
>> >  .commandtype = adCmdStoredProc
>> >  .execute
>> > end with

>> > set oCmd = nothing

>> > * Note that mOrder is a UDT.

>> > Any ideas or suggestions as to why I'm getting this error? Is there a
>> > certain DLL I am missing for Win98, or is this a platform problem? How
>do
>> I
>> > fix this?

>> > Thanks for the help.

>> > Regards,
>> > husky



Tue, 01 Feb 2005 00:00:53 GMT  
 
 [ 1 post ] 

 Relevant Pages 

1. VB6 application using SQL Server 2000 migrating db to SQL Server 2

2. Executing MS SQL Server 2000 stored procs via MS Access 2000

3. VBA problems Going from Windows 98 to Windows 2000

4. ExtCreatePen does not work in Windows 2000 but works in Windows 98

5. No Microsoft Transaction Server Type Library in Windows 2000 Advanced Server

6. doing updating from grid to sql server with stored procedure sql 2000

7. BUG: Visual Basic 6.0 T-SQL Debugger Fails Against SQL Server 2000 Named Instance (Q310647)

8. CR8+VB6+SQL Server 2000 and Windows 2000

9. CR6 and SQL Server 2000 and Windows 2000

10. Invalid Page Fault when connect to SQL Server 2000

11. Deploy dotnet windows application in windows 95/98

12. Application runs with Windows 95/NT, but doesn't work with Windows 98

 

 
Powered by phpBB® Forum Software