Date: Sat, 03 Jul 2004 07:50:30 -0400
From: JOHN KIDWELL
To: ALL
Subject: Wcreports
Newsgroups: win.server.wcreports
Message-ID: <1088855430.37.0@winserver.com>
X-Mailer: Wildcat! Interactive Net Server v7.0.454.5
Lines: 6

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

--- Platinum Xpress/Win/WINServer v3.1
* Origin: Prison Board BBS Mesquite Tx //telnet.RDFIG.NET www. (1:124/5013)

Date: Sun, 04 Jul 2004 02:36:52 -0400
From: HECTOR SANTOS
To: JOHN KIDWELL
Subject: Re: Wcreports
Newsgroups: win.server.wcreports
Message-ID: <1088923220.37.1088855430@winserver.com>
References: <1088855430.37.0@winserver.com>
X-WcMsg-Attr: Rcvd
X-Mailer: Wildcat! Interactive Net Server v7.0.454.5
Lines: 34

Thanks for the info.

But I think that is what the wcrdlls.exe "fixup" program was suppose to do
from the ftp.santronics.com ftp site? It installs this microsoft OCX and others and also REGISTER it.

Since you said you didn't have have to "REGISTER" it, it probably means
that you ready had it installed before, but it was somehow deleted or your registry or something is little mess up.

Basically what I am saying OCX files and DLL files with OCX behavior (all Microsoft stuff), are not just put into the directory and expected to work. They need to be registered, I believe with the REGSVR32.EXE program. If
this was a new OCX, just putting it there would not be correct.

Anyway others, like Mark Bappe, can better explain OCX better than me or explain why it worked for you without registering it. :-)

Glad you are back up with wcReport.

-- Hector




<JOHN KIDWELL> wrote in message news:1088855430.37.0@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

--- Platinum Xpress/Win/WINServer v3.1
* Origin: Prison Board BBS Mesquite Tx //telnet.RDFIG.NET www. (1:124/5013)

Date: Sun, 04 Jul 2004 08:40:21 -0400
From: DAVE GOURD
To: JOHN KIDWELL
Subject: Wcreports
Newsgroups: win.server.wcreports
Message-ID: <1088944821.37.1088855430@winserver.com>
References: <1088855430.37.0@winserver.com>
X-WcMsg-Attr: Rcvd
X-Mailer: Wildcat! Interactive Net Server v7.0.454.5
Lines: 12

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

--- Platinum Xpress/Win/WINServer v3.1
* Origin: Prison Board BBS Mesquite Tx //telnet.RDFIG.NET www. (1:124/5013)

Date: Mon, 05 Jul 2004 09:28:14 -0400
From: HECTOR SANTOS
To: DAVE GOURD
Subject: Re: Wcreports
Newsgroups: win.server.wcreports
Message-ID: <1089034325.37.1088944821@winserver.com>
References: <1088944821.37.1088855430@winserver.com>
X-WcMsg-Attr: Rcvd
X-Mailer: Wildcat! Interactive Net Server v7.0.454.5
Lines: 28

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


<DAVE GOURD> 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)

Date: Mon, 05 Jul 2004 09:57:59 -0400
From: "JOHN KIDWELL" <john.kidwell@winserver.com>
To: DAVE GOURD
Subject: RE: Wcreports
Newsgroups: win.server.wcreports
Message-ID: <1089035879.37.1088944821@winserver.com>
References: <1088944821.37.1088855430@winserver.com>
X-WcMsg-Attr: Rcvd
X-Mailer: Wildcat! Interactive Net Server v7.0.454.5
Lines: 23

Dave:
Yes, and the missing DLL's shown on re-install.
John




On 7/4/04 8:40 AM, DAVE GOURD wrote to JOHN KIDWELL:

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

--- Platinum Xpress/Win/WINServer v3.1
* Origin: Prison Board BBS Mesquite Tx //telnet.RDFIG.NET www. (1:124/5013)

Date: Mon, 05 Jul 2004 11:00:24 -0400
From: DAVE GOURD
To: JOHN KIDWELL
Subject: RE: Wcreports
Newsgroups: win.server.wcreports
Message-ID: <1089039624.37.1089035879@winserver.com>
References: <1089035879.37.1088944821@winserver.com>
X-WcMsg-Attr: Rcvd
X-Mailer: Wildcat! Interactive Net Server v7.0.454.5
Lines: 35

Thanks John (and Hector ).

Guess I missed messages/notifications of the fix/update.

Will uninstall and re-install wcreports and use the wcrdlls files to
see what happens here.

--
D

Dave:
Yes, and the missing DLL's shown on re-install.
John

On 7/4/04 8:40 AM, DAVE GOURD wrote to JOHN KIDWELL:

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

--- Platinum Xpress/Win/WINServer v3.1
* Origin: Prison Board BBS Mesquite Tx //telnet.RDFIG.NET www. (1:124/5013)

Date: Tue, 06 Jul 2004 16:54:10 -0400
From: "JOHN KIDWELL" <john.kidwell@winserver.com>
To: HECTOR SANTOS
Subject: Re: Wcreports
Newsgroups: win.server.wcreports
Message-ID: <1089147250.37.1088923220@winserver.com>
References: <1088923220.37.1088855430@winserver.com>
X-WcMsg-Attr: Rcvd
X-Mailer: Wildcat! Interactive Net Server v7.0.454.5
Lines: 44

Hector:
Thanks again,
John



On 7/4/04 2:36 AM, HECTOR SANTOS wrote to JOHN KIDWELL:

Thanks for the info.

But I think that is what the wcrdlls.exe "fixup" program was suppose to do from the ftp.santronics.com ftp site? It installs this microsoft OCX and others and also REGISTER it.

Since you said you didn't have have to "REGISTER" it, it probably means that you ready had it installed before, but it was somehow deleted or your registry or something is little mess up.

Basically what I am saying OCX files and DLL files with OCX behavior (all Microsoft stuff), are not just put into the directory and expected to work. They need to be registered, I believe with the REGSVR32.EXE program. If this was a new OCX, just putting it there would not be correct.

Anyway others, like Mark Bappe, can better explain OCX better than me or explain why it worked for you without registering it. :-)

Glad you are back up with wcReport.

-- Hector

<JOHN KIDWELL> wrote in message news:1088855430.37.0@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

--- Platinum Xpress/Win/WINServer v3.1
* Origin: Prison Board BBS Mesquite Tx //telnet.RDFIG.NET www. (1:124/5013)