The WCRDLLS.EXE at ftp.santronics.com should address this David. It has for
everyone for everyone reported RuntTime 13 and it didn't it was because of
some funky situation with the
OS and current registry settings.
OCX and things like it requires a GOOD proper setup with no REGISTRY issues.
I hope this isn't your issue, but all I can tell you is that the basic issue
is not have the proper OCX files. the WCRDLLS.EXE adds some in, and also you
need to make you use run WCREPORTSUPGRADE.EXE too if you can't it. But the
RUNTIME 13 was already solved with wcrdlls.exe.
--- Hector
wrote in message news:1088944821.37.1088855430@winserver.com...
>
> -> I finally found the problem with WcReports.
> -> I was missing a file called comdlg32.ocx.
> -> I found the file in some ancient backup cd's and put it in my
> -> windows/system folder and off she went. John Kidwell
>
> Which problem John ? - the runtime error 13 mismatch???
>
> --
> D
>
>
* Origin: Prison Board BBS Mesquite Tx //telnet.RDFIG.NET www. (1:124/5013)
|