|
-
Feb 21st, 2001, 10:45 AM
#1
Thread Starter
Addicted Member
Other programmers are testing my project today. No one had problems with running the project except one person. When they try to load the project, they get the following error:
Run-time error '430': Class does not support
Automation or does not support expected interface.
I have read all the help articles I can find, but none of them make any sense to me.
Does anyone know how to fix this?
Normal is boring...
 smh 
-
Feb 21st, 2001, 12:25 PM
#2
Member
I think ...
... it sounds like they didn't get all of your code, or are running it improperly.
What is the code you are running?
Does it activate another ActiveX that you created?
Does it use the correct version?
What is the project you are running, and where does the error activate?
Samwise Galenorn
[email protected]
-
Feb 21st, 2001, 12:27 PM
#3
Fanatic Member
If you are using ODBC, you might need to insure the correct version is installed on the client machine.
I got error 430 when I was developing using ADO 2.5, but one of my client machines was running ADO 2.1.
-
Feb 21st, 2001, 01:15 PM
#4
Thread Starter
Addicted Member
How do I find out the ado version is running on their computer? I am running 2.5.
Normal is boring...
 smh 
-
Feb 21st, 2001, 01:41 PM
#5
Thread Starter
Addicted Member
OK, never mind my last question because I have since then figured out that the problem is that I have ADO 2.5 and they have ADO 2.1. I have 2 questions:
Can I change the version on their computer when the program is installed?
If so, how?
Normal is boring...
 smh 
-
Feb 21st, 2001, 01:54 PM
#6
Fanatic Member
One option would be to choose the ADO 2.1 reference when you create your executable on the development PC.
-
Feb 21st, 2001, 01:58 PM
#7
_______
<?>
I haven't tried this but if you include the ADO 2.5 in your Package and Deployment would the install add it to the user's pc...overwriting the older version.
AddFile.
"A myth is not the succession of individual images,
but an integerated meaningful entity,
reflecting a distinct aspect of the real world."
___ Adolf Jensen
-
Feb 21st, 2001, 01:59 PM
#8
Fanatic Member
That is the other option. Either make a Setup package, or copy the mdac_typ.exe from the development PC to the client PC and run it to update the MDAC.
Posting Permissions
- You may not post new threads
- You may not post replies
- You may not post attachments
- You may not edit your posts
-
Forum Rules
|
Click Here to Expand Forum to Full Width
|