• Status: Solved
  • Priority: Medium
  • Security: Public
  • Views: 838
  • Last Modified:

Run-time error '430' : Class does not support Automation or does not

I've made a program in Vb6 when the database is on access 2000.
i've made an exe file and also made a setup file using the program setup specialist.
when i'm trying to run my prog on a computer that doesn't have vb installed i get the message "Run-time error '430' : Class does not support Automation or does not support expected interface"
i haven't made any new class for myself - in the project references i have word, access, outlook etc.
what can i do to run it on a computer with no vb????

please refer your answers to tweety2@inter.net.il as well as in the site.
Thanks a lot,
Yael
0
tweety2
Asked:
tweety2
1 Solution
 
RichWCommented:
http://www.microsoft.com/downloads/release.asp?releaseid=28337&area=top&ordinal=23

Download the VB 6 runtime files.  Load them ont he machine that doesn't have VB loaded.  Your program will then run.

RichW
0
 
Mohammed NasmanSoftware DeveloperCommented:
Hello

  also this error may happned if MDac not installed in the client machine, you can download the mdac from

www.microsoft.com/data
0
 
Richie_SimonettiIT OperationsCommented:
That's appears as version problem.
If you are using objects from Access, Word, Outlook, etc, End user machines must have those apps installed. It is not enought with TLBs only.
0
Concerto Cloud for Software Providers & ISVs

Can Concerto Cloud Services help you focus on evolving your application offerings, while delivering the best cloud experience to your customers? From DevOps to revenue models and customer support, the answer is yes!

Learn how Concerto can help you.

 
Richie_SimonettiIT OperationsCommented:
Also take a look at wich version of office you have in development machine and end user one.
If you are using, in example, Word 2000 and end user has, also in example, Word95/97, some methods/constants and other stuff from Word 2000 are not present in older versions.
0
 
tweety2Author Commented:
to Richie Simonetti
thanks for the comment, but the user and the end user has the same version of word, access and outlook, so it doesn't seem to be the problem.
0
 
bruintjeCommented:
this is probably not be the problem, but i would never distribute code containing hard references to office objects in a solution even if your're sure they're the same

-always develop with the references so you can use things like

dim objXL as Excel.Application

-and have the auto completion help you

-but distribute without references and code like

dim objXL as Object

-so you're not depending on versioning SP's etc.. on te client machine

HAGD:O)Bruintje
0
 
tweety2Author Commented:
to bruibtje
thanks, i did refer as x.application
0
 
tweety2Author Commented:
thanks
it worked wonderfully!
:O)
0

Featured Post

Industry Leaders: We Want Your Opinion!

We value your feedback.

Take our survey and automatically be enter to win anyone of the following:
Yeti Cooler, Amazon eGift Card, and Movie eGift Card!

Tackle projects and never again get stuck behind a technical roadblock.
Join Now