MComm control

  • Thread starter Thread starter Guest
  • Start date Start date
G

Guest

I have developed a system using the MsComm control on my Windows/98
(Access/98) and Windows/ME (Access/2000) systems. Both use the MsComm32.OCX.
My client runs Windows/NT but this control is not on their server or PCs. (
I don't have NT here so can't check it out here). Is there a different but
equivalent control for NT ? If not, can I safely copy the above OCX to his
system ? And will it give the same results as on my development systems ?
If I CAN copy it over safely, into which folder should I put it so that I can
register it in Access ? Sorry that is a lot of questions but any advice
would be greatly appreciated.
 
In my experience, just copying over the .ocx file and registering it should
work. The folder is not critical, C:\WINNT\System32 - which houses many
..ocx's anyway - should be a good choice.

HTH,
Nikos
 
Thank you. I will copy it over.

Nikos Yannacopoulos said:
In my experience, just copying over the .ocx file and registering it should
work. The folder is not critical, C:\WINNT\System32 - which houses many
..ocx's anyway - should be a good choice.

HTH,
Nikos
Click to expand...
 
hello again.

Have tried that. I found two files on my own Access/2000 system =
Mscomm32.ocx and Mscomm32.dep. Looked at the .dep and it seems to be saying
it needs Comcat.dll. So I copied all three over !. Unfortunately I still
can't see the "Microsoft communications control version 6.0" in the list when
I try to register it. Am I still missing something ? Do they need to
re-boot the server that I have copied the files to ?

Regards
DJW
 
To be honest, I don't know what the .dep file is, I have only ever done it
with the .ocx and that was enough. What puzzles me, though, is your mention
of the server. The .ocx is needed on the local PC that runs the Access app,
not on the server where the back end resides. Did you put it on the server
instead?

Nikos
 
Access is installed on the server AND each PC. I can only dial into the
server so I do my updates and testing there and, when all is OK, the customer
copies the front-end to each PC. I know I will need the MScomm32.ocx on each
PC, but I am trying to prove the solution on the server first. Hope that
makes sense.
 
Ok. When you go to register the .ocx on a machine (from within Access,
right?) you go Tools > ActiveX Controls, click on Register, locate the .ocx
file in the folder where you pasted it, select it and click OK. You
shouldn't be looking for the active X control name! It will appear in the
list only after you have registered the .ocx file.

HTH,
Nikos
 
Thanks again. I understand more now. BUT, having completed that process
seemingly successfully, I get "You don't have the license required to use
this ActiveX control". If you are not running out of patience with me, can
you help again please ?

D
 
Patience is no issue, but I'm afraid I don't have the answer. I've seen
several posts on it, though, so I'm confident you'll find the answer if you
seach the NG or google the error message.

Nikos
 
Thank you for all your help. I have used a big hammer approach and installed
Visual Basic v6 on their PCs. I knew that VB6 comes with MSComm32.ocx. The
system is now working fine.

Regards,

DJW
 
Well, that's a big hammer alright!

DJW of HSL said:
Thank you for all your help. I have used a big hammer approach and installed
Visual Basic v6 on their PCs. I knew that VB6 comes with MSComm32.ocx. The
system is now working fine.

Regards,

DJW
Click to expand...
 
Back
Top