|
-
Aug 31st, 2000, 04:02 AM
#1
Thread Starter
Fanatic Member
I have been developing an application which is now complete
I installed the application to the network last night and ran all but the report functions. Everthing has worked fine with the exception of the reports.
On the PC it was installed on it worked fine but if I try and access it from another PC I get the following error.
430: Class does not support automation or does not support expected interface.
Does anybody have any idea what this is?
When the application is installed any dll's, ocx's are installed to the app path. There should'nt be anything installed on the pc.
As I said earlier everthing else works. When the report is accessed the error is diplayed but the form will open but not display anything. The report is devloped with Crystal reports 'report designer control 6'.
Can you help?
Thanks
Gary Lowe 
VB6 (Enterprise) SP5
ADO 2.6
SQL Server 7 SP3
OK I know my spelling and grammer is crap so don't quote me on it!
To err is human to take the P! is only natural !!
Click on the top section of image for Marcus Miller website and bottom section of image for 'Run For Cover' sound clip

-
Aug 31st, 2000, 04:05 AM
#2
All COM objects (DLL and OCX) must be registred on the computer using the application even if it's not installed there.
-
Aug 31st, 2000, 04:09 AM
#3
Thread Starter
Fanatic Member
Joacim
Do you know how these can be registered by the app when it starts.
I know this can be done but can't remeber how it is done.
I know it done with regsrvr.
If I can get it to run off the network it would be a lot better.
Thanks
Gary Lowe 
VB6 (Enterprise) SP5
ADO 2.6
SQL Server 7 SP3
OK I know my spelling and grammer is crap so don't quote me on it!
To err is human to take the P! is only natural !!
Click on the top section of image for Marcus Miller website and bottom section of image for 'Run For Cover' sound clip

-
Aug 31st, 2000, 06:35 AM
#4
Fanatic Member
I received that exact same error after upgrading to VB SP4. The development machine references ADO 2.5 after upgrading, so you will need to run mdac_typ.exe on your target PC to upgrade it to ADO 2.5
Or change your application reference to ADO 2.1 and recompile the exe.
Option 2 worked for me. I did not want to upgrade the client machine until I knew more about the changes in ADO 2.5.
[Edited by jbart on 08-31-2000 at 07:39 AM]
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
|