Re: Configuration problem (help!)

Tech-Archive recommends: Repair Windows Errors & Optimize Windows Performance

On Dec 7, 8:07 am, "Dave O." <nob...@xxxxxxxxxxx> wrote:
If you installed pretty much any program that used these controls then they
would be available in the VB5 design environment, it may be easiest to copy
them over and register them with RegSvr32. However if you can find a copy I
think you'd be best off installing VB6.

Regards
Dave O.

<tadams...@xxxxxxxxx> wrote in message

news:e2762d73-cb51-4a81-b96b-c1ea60421140@xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx



On Dec 7, 4:55 am, "Dave O." <nob...@xxxxxxxxxxx> wrote:
You installed VB5 and then it complains about not being able to find
Microsoft Common Dialog Control 6.0 (SP3) & Microsoft Windows Common
Controls 5.0 (SP2). You know what the (SP2) and (SP3) mean?
Have you installed the service packs?

You may find that service packs for VB5 are rather thin on the ground, My
MSDN subscription does not go further back than VB6 so I don't have any
references. However you should be able to use VB6 with Service pack 5 or
6
all of which should be easy to source.

Regards
Dave O.

<tadams...@xxxxxxxxx> wrote in message

news:daf88bc5-8ba8-4e10-b5e6-58a4a0da16c6@xxxxxxxxxxxxxxxxxxxxxxxxxxxxxx

On Dec 6, 3:50 pm, "tadams...@xxxxxxxxx" <tadams...@xxxxxxxxx> wrote:
I am trying to recreate a runtime/development environment on a
different machine.

We are using VB5.

I have one running, but my network people say that they cannot just
clone it because of some sort of lock in of its network identity or
something.

So, I figured I would just load VB5 on the machine they gave me and it
would work. I figured loading the VB5 development system would
provide a run-time environment so I would not have to run setup to
install and reinstall our project, but it is not working.

I can't even run the code in the development environment, when I try:

1. It complains about not being able to fine comdlg32.ocx and
comctl32.ocx.

2. Controls that are check on the Project/Component/Controls menu in
the environment that works are *not even available to check* in the
new environment. They are:

Microsoft Common Dialog Control 6.0 (SP3)
Microsoft Windows Common Controls 5.0 (SP2)

Maybe I patched or cofigured the orginal working development
environment differently, but I don't recall doing anything except
running the VB5Cli.Exe patch and I did that on the new one.

Needless to say, my exe's will not run on this new system either. I
figured that installing the development environment would provide a
runtime environment as it does on the original system. But it exe
fails with run-time error 50003.

The old system has comdlg32.ocx in its System32 file. But the new one
has comdlg32.oca.

I can copy these files over to the new system, but do I have to do
more than that?- Hide quoted text -

- Show quoted text -

I don't recall installing any service packs. I am not sure why the
System32 files would be different.

I worked on development on the original box for a number of months and
I was a complete newbie when I started. Maybe I did something that I
don't recall doing, or some action caused these OCXes to be installed.- Hide quoted text -

- Show quoted text -

Problem solved!

Actually it was easy when I happened upon the solution. The VB
development environment was complaining that the OCXes were not in the
project directory. So I put them in the project directory. Then VB
opened the project without complaining and the runtime environment
seemed to be fixed by just opening the project, since the executables
started working without doing anything else.

This is pretty much a dedicated runtime environment so once I get it
working it should continue to work.

Thanks for your time.
.

Relevant Pages

  • Re: Some personal linux observations
    ... One of my big bitches about the M$ environment is that the command line ... but open source developers are usually more interested in expressing ... installing software from sourcecode. ...
    (alt.os.linux)
  • Re: Configuration problem (help!)
    ... If you installed pretty much any program that used these controls then they ... would be available in the VB5 design environment, it may be easiest to copy ... think you'd be best off installing VB6. ... You may find that service packs for VB5 are rather thin on the ground, ...
    (microsoft.public.vb.general.discussion)
  • Re: newbie configuration questions
    ... > developers have access to thier own systems without compromising the network ... > copied the development environment from another machine without knowing ... > You may get away with just installing SP5 but I would recommend reinstalling ... > MFC in the DLLs to statically linking to the Multithreaded libraries ...
    (microsoft.public.vc.language)
  • Re: Visual Studio stand alone (not installed) on build server.
    ... control of the build environment. ... This is done by avoiding installing ... by just running a script which copies the necessary files. ... I could do this type of XCOPY install of the compiler tools. ...
    (microsoft.public.vstudio.general)
  • Re: Microsoft Visual C++ Runtime Library Runtime Error
    ... It's better not to mess with system paths. ... file that would set the necessary environment variables and invoke the ... intercept API calls and if the app wants to write to a restricted location ... installing in C:\Program Files? ...
    (microsoft.public.windows.server.general)