Visual Foxpro cannot find support libraries 1

[ShyFoxBack]

Hy,
I have a little problem. I've made a program in visual foxpro 8.0 in the winxp os. When I run it in XP it works fine but when I want to open it in win98 it gives me the "Visual Foxpro cannot find support libraries" error.
I registered the vfp8renu.dll, vfp8t.dll, gdiplus.dll and when it comes to vfp8r.dll in 98 comes a strange error "VFP8r.dll may be corrupt" and I can't run the app.
If I remove it it gives me the "Visual Foxpro cannot find support libraries" error.
I register those dll's with regsvr32.exe and I put them in my app dir.
Where did I go wrong?
I also use some ocx files but they are registering well, all the problems come from foxpro runtimes.
Regards!

 

[Mike Lewis]

ShyFoxBack,

I don't know if this is relevant, but on my users' systems (running Win 98), those files are not stored in the app's fodler, but in Program files\Common Files\Microsoft Shared\VFP. You might try moving them there and re-registering.

Mike


Mike Lewis
Edinburgh, Scotland

My Visual Foxpro web site:

http://www.ml-consult.demon.co.uk

My Crystal Reports web site:

http://www.ml-crystal.com

 

[KDavie]

Did you manually add the dlls or did you use the merge modules?

-Kevin

 

[rgbean]

Minimally it could be msvcr70.dll. Checkout the information at

http://fox.wikis.com/wc.dll?Wiki~VFP8RuntimeFiles.

Any reason you aren't using a real Windows installer like the Free InstallShield Express that comes with VFP 8.0?

Rick

 

[Mike Lewis]

To follow up Rick's comment ...

I had a problem the other day, which I traced to InstallShield Express not installing msvcr70.dll, even though I specified all the right merge modules. I manually copied msvcr70.dll to target machine, and didn't bother to register it, and everything was fine. In that case, I did copy the file to application directory.

However, the error message was not the one that ShyFoxBack saw. It was just a straight "Cannot find msvcr70.dll" or something similar.

Mike


Mike Lewis
Edinburgh, Scotland

My Visual Foxpro web site:

http://www.ml-consult.demon.co.uk

My Crystal Reports web site:

http://www.ml-crystal.com

 

[ShyFoxBack]

HY,
STILL I WOULD LIKE TO KNOW WHY FOXPRO TELLS ME THAT MY VFP8R.DLL IS CORRUPT WHEN I TRY TO REGISTER IT WITH REGSVR32.EXE.
IS THERE A PROBLEM IF I COMPILE IT IN WINDOWS XP AND RUN IT IN WINDOWS 98 SE?
MUST I COMPILE IT IN WIN 98 TO WORK IN WIN 98?
REGARDS

 

[Mike Lewis]

Shyfoxback,

MUST I COMPILE IT IN WIN 98 TO WORK IN WIN 98?

In general, no. You can compile under any supported version of Windows and run under any other.

Mike


Mike Lewis
Edinburgh, Scotland

My Visual Foxpro web site:

http://www.ml-consult.demon.co.uk

My Crystal Reports web site:

http://www.ml-crystal.com

 

[rgbean]

ShyFoxBack,
That Wiki link (

http://fox.wikis.com/wc.dll?Wiki~VFP8RuntimeFiles)

is very careful to note that the order you register the .DLLs in is important.

Of course you don't have to compile your app under W98 for W98 - Win98 ISN'T a supported development environment under VFP 8.0+!

Rick

 

[ShyFoxBack]

Thank you!

rgbean (Programmer)
As I looked better I found that I wasn't registering one dll
gdiplus.dll. Now my application is working. you deserve a star for pointing me again to a helpfull site.
Star for you.
Thank you, again.

Regards.

 

[tondi]

Is it really necessary to 'register' the DLLs on end user systems? We've have no problem running with the DLLs located in APP folder without registering them.

 

[Mike Gagnon]

Tondi

You may want to read this faq184-2644

Mike Gagnon

If you want to get the best response to a question, please check out FAQ184-2483 first.

 

[tondi]

Thanks Mike,
How can there be 'confusion' if the runtimes are in the same folder as the EXE which is where Fox looks first?
Tony

 

[michaelkatz]

Just an additional note regarding the MSVCR70.dll.

For some reason, Installshield installed it in the root. This may have worked fine when the root was part of the "Path."

When running installshield: Under "Distibutables", right click the runtime library and select "Configure Merge Modules" and change the value to "System Folder."

This worked for me.
Michael

 

[Mike Gagnon]

Tondi

How can there be 'confusion' if the runtimes are in the same folder as the EXE which is where Fox looks first?

[ol][li] Dr. Ed Rauh was a brilliant FoxPro programmer who passed away last year, and I have feelling that if he says "register the Dlls ortherwise it can cause problem", I tend to believe that, since he was always very throurough with was he said. [/li]
[li] in the case of a DLL, my understanding is that VFP looks in the registery first, then in the application path. Only to "slow down" the process of loading the application.[/li]
[li] when you install VFP itself on a computer, the runtime DLLS get registered, why would you think that an application would be any different?[/li]
[li] If Microsoft, most (if not all) seasonned programmers and gurus says "Register the runtime DLLS", why would not registering them be a better option?[/li]
[li] when you use the Setup Wizard or InstallShield to install an application, the DLLS get registered.[/li]
[li] most commercial software when the get installed, register their DLLS, why would VFP be any different?[/li][/ol]

P.S. One day you will install an application on a user's computer and find it alot slower than the version on your development machine, and you might not think of "Maybe I should have registered the DLLS". And start looking to code optimization.
Registering a DLLS takes one line of code, why try to get away with not doing it?

P.P.S.I don't really have the time to research the specific technical reasons, but I'm sure there are articles on the NET that describe in details, the reasons for registering versus not registering.





Mike Gagnon

If you want to get the best response to a question, please check out FAQ184-2483 first.

 

[michaelkatz]

Wouldn't registering be required on all workstations?

Having the file reside in the application folder should make them available to all workstations.

Michael