MSRD020.DLL

[David G. McDivitt]

I need for users to change their password on an SQL server. NT
authentication is not used. I copied a piece of code from the Microsoft
site to accomplish this. Upon running it I get run-time error 429,
"ActiveX component can't create object". Since help indicated a DLL
might not be registered, I looked at the VB project header, found
MSRD020.DLL listed, but cannot find this on my computer anywhere.

The code example uses RDO. In the references dialog I included
"Microsoft Remote Data Object 2.0", which eliminated all syntax errors
in the code. I am curious why STDOLE2.TLB is present on my computer,
providing references, but MSRD020.DLL is not. I am using VB 5.0.

I did a search at the Microsoft site to find MSRD020.DLL with no
success. I also searched the web and deja.com with no success. It is my
hope I can copy this to my computer, register it, and have the code run.
I have a feeling this was intended for VB6, since most articles at the
Microsoft site refer to VB6 when mentioning RDO, though a couple did
refer to VB5. Whatever the case, I want to put it on my computer and see
what happens.

Assistance would be appreciated. Thanks

--
dmcd...@yahoo.com
http://www.members.tripod.com/dmcdivitt
http://www.geocities.com/dmcdivitt

[Tore]

Since you have the reference to "Microsoft Remote Data Object 2.0", the file
should exist on your computer.

It may be a simple case of confusing the letter O with the digit 0.

Try looking for msrdo20.dll. This file is distributed with VB (5 and 6),
but possibly not with the Learning Edition.

For distributing your app you need to use a setup program to help ensure
that you get all the correct support files, and that you don't copy over
newer versions on a target system.

HTH,
Tore.

David G. McDivitt <noemail@address> wrote in message
news:f4k21tg2tui5dn7ch...@4ax.com...

[David G. McDivitt]

Thanks for that info. I found msrdo20.dll after giving it the correct
spelling, and it is on the computer. I registered it to make sure, but
my problem has not gone away.

The code with a problem is:
Dim Environment As rdoEnvironment
Set Environment = rdoEnvironments(0)

I get no syntax errors, but when I run the code I get the following:
Run-time error '429': ActiveX component can't create object

At the Microsoft site, problems are mentioned with RDO and VB5, and it
says Visual Studio 97 Service Pack 3 will fix those problems. I had
already installed this once, but I installed it again to no avail.

When I highlight "rdoEnvironments" and press F1, it cannot find
rdo96.hlp, and it is not on the computer. Would be nice to have that. I
have VB5 Professional Edition.

The error I get is an ActiveX error, but there are no OCX references in
the project. I did see mention of msrdo20.ocx and msrdc20.ocx at the
following two locations:
http://support.microsoft.com/support/kb/articles/Q176/4/28.ASP
http://msdn.microsoft.com/library/psdk/dasdk/mdac3df7.htm

At another location it says to install ODBC from the VB install CD:
http://support.microsoft.com/support/kb/articles/Q176/4/28.ASP
I did that and there is no difference.

[Tore]

The following lists a number of possibilities for your situation:

1: Article "PRB: Program Generates Error 429 on First Reference to RDO"
(ID: Q181852) may apply to your situation. This could be the case for
instance if you installed an older version of an ODBC driver after
installing RDO (with VB5 or MDAC...).

2: What OS are you using? In Win9x, is it possible that you exceeded the
maximum registry size when installing Visual Studio? I have seen this
happen when installing everything on an already software-rich system.

3: It is possible that you may have had a file system corruption and lost
or corrupted some DLL's.

4: An ill-behaved install program has overwritten some DLL's with an
incorrect/incompatible version.

5: You didn't include RDO and/or a related option when you installed VB5.

RDO depends on a number of DLL's to be present (installed an registered
properly) on your system. While you could attack the DLL's and OCX'es
piecemeal, it is usually better to perform a full install of the missing
item(s), in this case the RDO (Data Access) distribution set. Either
reinstall VB5, or obtain an updated MDAC (Microsoft Data Access Components)
which also includes RDO, and install it. Note that if you have a prior
version of MDAC install, and reinstall VB5, you may need to reinstall the
MDAC version as well (I'm not sure about this). On Win9x, MDAC also
requires that you install DCOM.

HTH,
Tore.

David G. McDivitt <noemail@address> wrote in message

news:cdc51t8kui5foi0qq...@4ax.com...

[David G. McDivitt]

The code I am trying to run is located at:
http://support.microsoft.com/support/kb/articles/Q172/5/78.ASP

I do not have msrdo20.ocx on the computer. Do I need that? It was
mentioned at the Microsoft site. One would think if needed, it would be
installed though.

You mentioned piecemealing the various components together, as an
option. I'm willing to try that since I have gone through complete
removal and reinstallation. Do you have any suggestions in this regard?

I also did the control registration fix for licensing problems. That
didn't help either.

In answer to your points:

1) I deleted VB and Access from the computer and reinstalled only VB,
including updates, then MDAC. I tried the program following each step
and it continued giving the same error. The file msrdc20.ocx was
installed and registered but msrdo20.ocx was never installed.

2) I am using Win95. That's the only thing allowed at this location.
Visual Studio was not installed, but VB 5.0 Professional. I do not feel
the registry size has been exceeded since I try and keep most stuff
cleaned off, and the registry is much smaller here than on my home
computer, for instance. I installed everything in the sequence mentioned
in #1 above. In the VB install there is no RDO option, just a data
access option, though msrdo20.dll does exist on the CD and is included
with data access stuff.

3-4) I reinstalled everything.

5) I loaded everything that came with VB5 Professional.

[Tore]

I guess it's back to basics:

1: Ensure your system's integrity:
- Run ScanDisk to eliminate any lost clusters or file conflicts.
- Run a Virus Checker from a clean bootable disk.

2: Uninstall MDAC, etc.
3: Uninstall VB5
4: Reinstall VB5
5: Reinstall VB5 SP3
6: Reinstall DCOM95
7: Reinstall MDAC

8: Load your project
9: Remove the reference to RDO
10: Save the project
11: Exit VB
12: Restart VB
13: Load your project
14: Re-add the RDO reference to the project
15: Save and test.

MDAC requires DCOM. Did you install DCOM on the PC? DCOM95 is available
from http://www.microsoft.com/com/dcom/dcom95/dcom1_3.asp.

You can try installing DCOM (and then reinstall MDAC) first.

If you want to try a piecemeal approach after this, you should have the
following files in your System32 directory:

Msrdo20.dep
Msrdo20.dll
Msrdo20.srg

The first will show the dependencies for Msrdo20.dll. The last is a
registry script with the license key for Msrdo20.dll. There is no
Msrdo20.ocx.

Also, you can open your project, and check the Object Browser (F2) for a
reference to RDO. Select it, and it will show you where the currently
"active" Msrdo20.dll is.

There is an unsupported tool "Dependency Walker" on the VB5 CD. Use it to
determine what DLL's etc. are required.

HTH,
Tore.

David G. McDivitt <noemail@address> wrote in message

news:g0181t4b3jssp51bd...@4ax.com...

[David G. McDivitt]

Well, didn't work. I also tried running the code on my machine at home. On
it I have VB5 Professional as well, with Win98SE. It would make sense if I
install everything from scratch and in the PROPER order, it should work.
Surely if they put the code out there it will function.

At home I did not find msrdo20.srg. I think I remember seeing it on my
machine at work but don't remember.

I guess I need to come up with an alternate approach such as making direct
calls on the ODBC API. Know where I can find a code snippet for that and use
sp_password?

[Tore]

Why not use ADO? The key to the article seems to be the sp_password stored
procedure.

I don't know why you can't get RDO to work - and it would bother me to not
figure it out, since there is a reason for it buried somewhere. I'd hate
for it to come back and bite me in a production situation...

HTH,
Tore.

"David G. McDivitt" <dmcd...@yahoo.com> wrote in message
news:hmv81t0r5rsqjtru0...@4ax.com...

[David G. McDivitt]

My goal was to create a code snippet I could easily include in several
Access 97 applications, placing it behind a "password" button. I was able to
reference the ADO objects which come with MDAC 2.5, and the code works just
fine. The help file won't automatically come up since it's in a different
format, but I can open it standalone and look things up. The help file can
be obtained by downloading the VB6 upgrade and picking through the files.
All I needed was an ADO connection object so I could call sp_password. The
rest of the application, which uses DAO, is not affected at all. The connect
string is constructed from DAO tabledefs.

I don't know why RDO won't work in VB5 or Access 97, but that's a moot point
now. I just happened to try that approach first. Thanks for the help.