| Title: | Microsoft Visual Basic |
| Moderator: | TAMARA::DFEDOR::fedor |
| Created: | Thu May 02 1991 |
| Last Modified: | Thu Jun 05 1997 |
| Last Successful Update: | Fri Jun 06 1997 |
| Number of topics: | 2565 |
| Total number of notes: | 10453 |
I am encountering an issue with the VB Setup Wizard in 4.0. When
running my VB application on an Intel machine that has the VB
development software installed, it runs fine. However, when I create
an installation kit using the Setup Wizard and install it on our Intel
server (which does not have VB development software), it will not run.
It does not like the RDO objects in the application, and I get the
following VB error:
Error Number 424 - Object required
The application uses RDO to make SQL Server calls.
I verified that the kit contains the RDO object library (MSRDO32.DLL),
which I have included as a reference in the application. The setup kit
also appears to include the VB runtime files. However, something else
must be missing from the kit that is needed??? Anyone have any ideas?
Rgds,
Cheryl
| T.R | Title | User | Personal Name | Date | Lines |
|---|---|---|---|---|---|
| 2522.1 | You probably need ODBC as well | EVTSG8::TOWERS | Fri Mar 21 1997 05:03 | 4 | |
Did you install SQL Server ODBC drivers in the kit?
Cheers,
Brian
| |||||
| 2522.2 | ODBC SQL Server drivers already there... | YAZ67::DIAS | Mon Mar 24 1997 10:42 | 18 | |
I didn't have to because the ODBC SQL Server drivers were already
installed on the server where I was installing the VB kit. However, the
following ODBC files were automatically included in my VB kit by the setup
wizard:
ODBCJT32.DLL
ODBCJI32.DLL
ODBCTL32.DLL
Is there some other ODBC file that I could be missing? It is very
difficult to find enough info on ODBC and what is required for VB to
access SQL Server successfully.
I will doublecheck what ODBC files I can find on the server versus the
files on the client from which the application is working fine.
Rgds,
Cheryl
| |||||
| 2522.3 | XSTACY::imladris.ilo.dec.com::grainne | Grainne Ni Choiligh | Wed Mar 26 1997 13:20 | 5 | |
Don't you need the SQL Server ODBC Driver SQLSRV32.DLL ? I have it on my machine, I think it was actually installed by Microsoft IIS v3.0 Active Server Pages which I installed before VB v4.0 but I imagine you'd still need it ? | |||||
| 2522.4 | I have the ODBC driver...but what else? | TIANT::DIAS | Thu Mar 27 1997 12:33 | 13 | |
Yes, that ODBC Sql Server driver was already installed on the server.
What I am not sure of is what other ODBC files are needed beyond the
driver (and if any are missing).
It is still possible that it is not an ODBC file at all that is
missing. It clearly is a file that is needed for RDO commands, besides
the RDO object library file MSRDO32.DLL.
Is it documented anywhere what DLL and OCX files are needed for an
application when you are performing certain tasks?
Rgds,\
Cheryl
| |||||
| 2522.5 | OSAV04::UMEZAKI | Yasushi Umezaki,SWS-Japan | Tue Apr 01 1997 21:24 | 22 | |
Hi,
I have the similar problem with MSRDO32.DLL and VB setup wizard.
In my case, I found "$(DLLSelfRegister)" missing for MSRDO32 in setup.lst.
[Files]
File=1,SPLIT,MSRDO32.DL1,MSRDO32.DLL,$(WinSysPath),,$(Shared)...
|
v
File=1,SPLIT,MSRDO32.DL1,MSRDO32.DLL,$(WinSysPath),$(DLLSelfRegister),$(Shared)...
One more caution, if MSRDO32.OCX remains in the windows system directory by
the failed setup, setup.exe does not do with $(DLLSelfRegister). To avoid this,
you can delete MSRDO32.OCX before running setup.exe with the modified setup.lst.
Hope this helps.
Regards,
Yasushi Umezaki
| |||||
| 2522.6 | there was no msrdo32.ocx file, though | CRUISE::JBONIN | PSG/IW Consulting Services | Fri Apr 04 1997 14:46 | 6 |
I have been researching this problem for Cheryl while she is on
vacation, and it seems that the missing $(DLLSelfRegister) was
the culprit.
Thanks
John
| |||||