Re: Running two versions

Mike McDowall wrote:
Thanks for the ideas everyone.

On Thu, 17 May 2007 10:34:27 +0200, "Stefan Wuebbe"
<stefan.wuebbe@xxxxxx> wrote:

"Mike McDowall" <m.a.mcdowall@xxxxxx> schrieb im Newsbeitrag news:m2un435m23eabreq1hr4nh69gov9ln0q67@xxxxxxxxxx
I have VFP9 SP1 on a machine. I have recently installed VFP5 for
legacy work. When I start 5 (development environment or .exe compiled
in 5) I get an error "Error initializing Application object". Click OK
and everything does work fine, but it is a bit annoying.
In general, different VFP versions can co-exist on the same
machine w/o any problems. In particular Vfp5/6/7/8/9 do so in
practise for me, runtimes as well as the IDEs, as long as you do
install each of them in its own (default) directory.
(And as long as you do not share "system" files, like foxuser.*
in different versions.)
Will certainly look at that - suspect they may be using the same
foxuser.

Your quoted error message sounds as if could be a custom one
(e.g. there is at least one similar in the MS "Wizard" framework
if I recall correctly).
On the other hand, there is a native one too, Help says :
Error initializing Application object (Error 1574)
The Automation server or type library is not registered correctly.
Your registry file is corrupted.
Remove the registry entry.
If it's a native one, can you click "Help" in the dialog to get into
the VFP help chapter?
Or when it's a custom one, can you click "Suspend" in the dialog
and see the offending line in the debugger?
It is the native one, soon as I start the application. It only has an
OK button - no help.

If the latter and if the error occurs when starting the IDE too, have a
look at "Startup Program" in "Options"/"File Locations"
/ or a config.fpw file containing a line like "command=..."
/ or a project hook bound to the project being started automaticall if any
/ or additional parameters hidden in your desktop shortcut if you use one
to start the IDE.
IOW, anything that might possibly contain custom code running at
startup.
I'll look at this too.

If the former, it sounds like a VFP setup issue that I do not have seen
myself yet. See if un- and reinstalling VFP (the oldest version first
and the latest last) helps.
Sounds a likely cause. 9 was installed first, 5 much later. However,
this is a hospital machine and ordinary folk, even application
programmers don't get admin rights. I don't even have the 9 install
disk. Further, hospital IT will probably be too busy to notice a
request like this till after I have moved on from VFP ...

Cheers,
Mike.
Actually that might be the issue. If VFP5 was installed without admin rights you may get that type of error. It might be as simple as getting someone with admin rights to re-install VFP5 to get it to work. Remember when VFP5 was out, everybody always had admin rights, so they are pretty much assumed.

--
Cy Welch
89 Camaro RS 5.0 TBI
03 Malibu
.