To all that responded regarding this issue, thanks so much! The
suggestion to simply put the VFP9 dlls in the folder with the .exe is
working well and provides a great and easy way for me to eventually
move to SP2 or perhaps back to SP1 someday..
PS - Thanks to Rick Schummer for his terrific
PROTECTED] On Behalf Of Steve Ellenoff
Sent: Thursday, November 06, 2008 03:51 PM
To: [EMAIL PROTECTED]
Subject: Re: Can VFP9 SP1 SP2 runtimes co-exist happily?
To all that responded regarding this issue, thanks so much! The
suggestion to simply put the VFP9 dlls in the folder with the .exe is
working
Rick Schummer wrote:
VFP will find the runtimes in the application folder before even
looking in the
common folder. So, it'll load a smidgen faster by putting the runtimes
in the
application folder.
Depends, naturally. If the app folder is on the network and has to pull
it over wire, the
Different strokes for different folks.
Why go through the unnecessary network overhead?
Loader apps work well *most* of the time, but there is one reason I like a
mechanism (manual or
automated) to kick people out of the app: it ensures they are running the
current one. Case in
point: rogue
I wouldn't dream of running the app on the server anymore, ever since 1999
when I learned about
the LOADER idea from others here on ProFox.
So how do you ensure the user is running the loader and not the local EXE? Have
you taken the
precaution of adding versioning logic to the app startup
Rick Schummer wrote:
I wouldn't dream of running the app on the server anymore, ever since
1999 when I learned about
the LOADER idea from others here on ProFox.
So how do you ensure the user is running the loader and not the local
EXE? Have you taken the
precaution of adding versioning logic
Rick Schummer wrote:
I wouldn't dream of running the app on the server anymore, ever since 1999
when I learned about
the LOADER idea from others here on ProFox.
So how do you ensure the user is running the loader and not the local EXE?
Have you taken the
precaution of adding versioning
Besides, disk space is cheap so there's no need to rely on the old approach
of having it exist in
one spot and using the registry for that reference.
Depends. Some of us still prefer run times on client machine for performance.
In this case you
really should have them installed in common
Rick Schummer wrote:
Besides, disk space is cheap so there's no need to rely on the old approach
of having it exist in
one spot and using the registry for that reference.
Depends. Some of us still prefer run times on client machine for performance.
In this case you
really should have
Rick Schummer wrote:
Depends. Some of us still prefer run times on client machine for performance.
In this case you
really should have them installed in common folder to make things simpler.
VFP will find the runtimes in the application folder before even looking in the
common folder. So,
Rick Schummer wrote:
All feedback on this topic welcome and appreciated-
Runtime files are named identical for a major release of VFP, so your
SP1 and SP2 runtimes are
identically named. No way around that.
I agree with Paul and Andrew in this situation about putting the
runtimes in the
Are you saying that it would perform better if you had installed the
runtimes in the common
folder?
You are thinking the app and the runtimes are on the same machine. I normally
think of it as running
off a network server. On the same machine we are talking small differences, but
over a
VFP will find the runtimes in the application folder before even looking in
the
common folder. So, it'll load a smidgen faster by putting the runtimes in the
application folder.
Depends, naturally. If the app folder is on the network and has to pull it over
wire, the commons
folder even being
Rick Schummer wrote:
VFP will find the runtimes in the application folder before even looking in
the
common folder. So, it'll load a smidgen faster by putting the runtimes in the
application folder.
Depends, naturally. If the app folder is on the network and has to pull it
over wire,
Paul McNett wrote:
Rick Schummer wrote:
VFP will find the runtimes in the application folder before even looking
in the
common folder. So, it'll load a smidgen faster by putting the runtimes in
the
application folder.
Depends, naturally. If the app folder is on the network and has to
Steve Ellenoff wrote:
I'm moving an app from VFP8 up to VFP9 and am still unsure of SP2.
Wanted to know if anyone knows how well SP1 2 run-time files exist
on a client's machine. Obviously different versions of VFP have no
trouble as the naming is different for the dlls, but I'm not sure
Steve Ellenoff wrote:
I'm moving an app from VFP8 up to VFP9 and am still unsure of SP2.
Wanted to know if anyone knows how well SP1 2 run-time files exist
on a client's machine. Obviously different versions of VFP have no
trouble as the naming is different for the dlls, but I'm not sure
By application directory I assume you mean the directory where the
.exe will live. So are you simply copying the VFP9 runtime files? I
was under the impression that you could no longer just do that since
VFP8? IIRC the dll has to be registered with windows either through a
setup program or
Steve
I also just put the runtime files into the .exe folder.
The only file I register is the help file.
Using VFP9 with SP1
Andrew Stirling
01250 874580
http://www.calcpay.co.uk
HMRC Accredited UK payroll program
Steve Ellenoff wrote:
By application directory I assume you mean the directory
Yes, I've been reading Rick's whitepaper on how to have SP1 SP2
co-existing on my Development machine, link is actually here:
http://rickschummer.com/blog/2008/03/vfp-9-rtmsp1sp2-one-machine.html
but I didn't see it mention the run time files which is what prompted
the question..
(Obviously if
All feedback on this topic welcome and appreciated-
Runtime files are named identical for a major release of VFP, so your SP1 and
SP2 runtimes are
identically named. No way around that.
I agree with Paul and Andrew in this situation about putting the runtimes in
the folder with your
Steve Ellenoff wrote:
By application directory I assume you mean the directory where the
.exe will live. So are you simply copying the VFP9 runtime files? I
was under the impression that you could no longer just do that since
VFP8? IIRC the dll has to be registered with windows either
Thanks to everyone for their help and suggestions on this. I look
forward to trying it out soon.
At 03:07 PM 11/03/2008, you wrote:
All feedback on this topic welcome and appreciated-
Runtime files are named identical for a major release of VFP, so
your SP1 and SP2 runtimes are
identically
23 matches
Mail list logo
