Registering comdlg32.ocx in windows 2000

[Andy Berry]

I've written some interface with comdlg32.ocx in a PowerPoint application.
In windows 2000, with admin privileges, I can register comdlg32.ocx with an
installer and the process works fine when logged in as an administrator.
Problem is, when logged in as a user, the forms I've written give a warning
that parts of the form couldn't be loaded because the file does not exist.

If anyone can help me, please... I can't figure this one out.

Is office developer a solution? Or is the .ocx possibly outdated? how can
I find a current one?

Thanks for your time and help!

 

[Steve Rindsberg, PPTMVP]

Andy,

You might have to register the control (or just rerun the installer) while
logged on as a user.

A bit more complicated for you but a lot more stable in the long run would
be to use WinAPI calls directly instead of letting the OCX do the job for
you. Go to www.mvps.org and from there follow the link to Randy Birch's
VBNet site. There are plenty of Common Dialog API code examples there;
they'll run as-is or with a bit of modification in PowerPoint.


--

Steve Rindsberg PPT MVP
PPTLive ( http://www.pptlive.com ) Featured Speaker
PPTools: http://www.pptools.com
PPT FAQ: http://www.pptfaq.com

 

[Andy Berry]

Steve,

Thanks for your response and the link. I was trying to keep it simple
and easily portable by using a 'common' dialog. I've learned though that
may have not been the way to go with having to register the .ocx.

I have been using some API calls, but I require guidance for that, so
thank you for the link. I will update my code to use them.

I solved my problem after a little more research ... the Windows 2000
was installed under a NTFS system. While registering the control,
administrators and 'power' users were only allowed access to the control. I
had to go into the file itself and allow all users access. Seems pretty
simple, but it was hidden from me for quite a while and made it frustrating.
Now everything works great, but I'm afraid the installer won't create this
authorization, its a great freeware program, but not very powerful
(apparently). So I'll have to give user's a little FAQ file or something to
help them out.

Thanks again and I'll be checking out the API calls. I am learning --
lots has changed since my CS degree over 13 years ago.

Rock on.

Andy

Andy,

You might have to register the control (or just rerun the installer) while
logged on as a user.

A bit more complicated for you but a lot more stable in the long run would
be to use WinAPI calls directly instead of letting the OCX do the job for
you. Go to www.mvps.org and from there follow the link to Randy Birch's
VBNet site. There are plenty of Common Dialog API code examples there;
they'll run as-is or with a bit of modification in PowerPoint.


--

Steve Rindsberg PPT MVP
PPTLive ( http://www.pptlive.com ) Featured Speaker
PPTools: http://www.pptools.com
PPT FAQ: http://www.pptfaq.com

 

[Steve Rindsberg, PPTMVP]

Thanks for your response and the link. I was trying to keep it simple

and easily portable by using a 'common' dialog.

That's exactly the point of my suggestions; couldn't be more in agreement
over that goal.
I think you'll find using the common dialog stuff simple enough.

Thanks again and I'll be checking out the API calls. I am learning --
lots has changed since my CS degree over 13 years ago.

Give Randy's site a good looksee and allow yourself an hour to get the
common dialog calls working. That's about all it took me, and my only
formal programming course was a quarter of nightschool FORTRAN 30-some years
ago. You're way ahead 'o me. ;-)