- Original Message -
From: Grigore Dolghin
To: profox@leafe.com
Sent: Saturday, January 31, 2009 5:16 PM
Subject: Re: VFP 9 runtime on Vista, the QD way
Here is a innosetup script which deals with everything regarding installing
a visual foxpro application under vista, in program
Paul McNett wrote:
Charlie Coleman wrote:
The only downside is if you need to update the OCX itself - e.g. going
to a
later version of the OCX. In that case, they'd have to do the big
install
again.
I'm glad I took the position of never relying on too many third-party
libraries. The
only
Rick Schummer wrote:
As I stated in my previous post, I don't care whether the client wants
to run from the server or the
local workstation. All your points have been discussed, and likely
debated with IT Managers the
world over, but in the end it is their responsibility to maintain and
support
Paul McNett wrote:
- Absolutely guarantees everyone will run the same EXE (no local copies
on workstation with previous
bugs because launcher failed)
Taken care of by your exe refusing to start if the version the version
recorded on
the server.
That's how Sylvan legacy app does it. And
Vince Teachout wrote:
Eurico Chagas Filho wrote:
Hi Vince
Remember that talk about a loader program ?
Well I got a setup just like that, I only update the server and
the loader takes cares of updating the stations.
I had to twist a little because I have different data, depending
on the
On Mon, Feb 2, 2009 at 9:06 AM, Charlie Coleman colem...@acm.org wrote:
ROFL. Where have you been? The viruses are all still around, popping in
through IE use, MS Outlook emails, Windows security holes, blah blah blah.
Maybe the problem is we've just never GOT OUT OF the 90's with Windows.
Stephen Russell wrote:
On Mon, Feb 2, 2009 at 9:06 AM, Charlie Coleman colem...@acm.org wrote:
ROFL. Where have you been? The viruses are all still around, popping in
through IE use, MS Outlook emails, Windows security holes, blah blah blah.
Maybe the problem is we've just never GOT OUT OF
On Sun, Feb 1, 2009 at 12:34 PM, Whil Hentzen
list...@softwaremuscle.com wrote:
In addition to Rick and Rick's comments I sure encourage customers
to 'have it their way', whatever their way is. I mean that's why
they're hiring ME - so they can have it THEIR way, not the way some
Charlie Coleman wrote:
At 09:15 PM 1/31/2009 -0600, Stephen Russell wrote:
On Fri, Jan 30, 2009 at 3:01 PM, KAM.covad
a_gmail_nos...@kenmcginnis.com wrote:
Installing on the local machine will not work for my clients. I have
tried it. It is a mess. If you have 8 workstations, you would have
Grigore Dolghin wrote:
I am sorry, I strongly disagree. They are hiring me to give them the best
option, and this isn't always THEIR way.
That's kinda what I was eluding to as well. If they go against what I
propose, I document it so as to not have it held against me later, but I
won't walk
Ed Leafe wrote:
On Feb 2, 2009, at 9:10 AM, MB Software Solutions General Account wrote:
Nor do I really care if they're paying me regardless. But my job,
as
the IT professional providing my services, is to explain the pros and
cons of each approach, and I can tell you from those
On Feb 2, 2009, at 9:25 AM, MB Software Solutions General Account wrote:
See my recent reply. It takes a bit more than just this issue (run
it
on the server!) but if there's enough, yeah, I fire them and walk
away.
On one occasion I got a call from a company I had dropped about
[MB wrote:]
Rick Borup's session on installers at WhilFest years ago
suggested this, iirc. (Well, not exactly a BIG app but
rather a lightweight one that had all the runtimes.) He'd
deploy something like a notebook/notepad/calendar app that
was basic but contained the runtimes, and then
Charlie Coleman wrote:
The only downside is if you need to update the OCX itself - e.g. going to a
later version of the OCX. In that case, they'd have to do the big install
again.
I'm glad I took the position of never relying on too many third-party
libraries. The
only OCX I ever relied on
MB Software Solutions General Account wrote:
Paul McNett wrote:
- Absolutely guarantees everyone will run the same EXE (no local copies
on workstation with previous
bugs because launcher failed)
Taken care of by your exe refusing to start if the version the version
recorded on
the server.
On Feb 2, 2009, at 9:10 AM, MB Software Solutions General Account wrote:
Nor do I really care if they're paying me regardless. But my job,
as
the IT professional providing my services, is to explain the pros and
cons of each approach, and I can tell you from those experiences I've
had in
I am sorry, I strongly disagree. They are hiring me to give them the best
option, and this isn't always THEIR way.
On Sun, Feb 1, 2009 at 8:34 PM, Whil Hentzen list...@softwaremuscle.comwrote:
It isn't always the developer's choice. In my experience, some clients
will insist on the app being
At 09:15 PM 1/31/2009 -0600, Stephen Russell wrote:
On Fri, Jan 30, 2009 at 3:01 PM, KAM.covad
a_gmail_nos...@kenmcginnis.com wrote:
Installing on the local machine will not work for my clients. I have
tried it. It is a mess. If you have 8 workstations, you would have to
update all 8 at the
On Mon, Feb 2, 2009 at 9:21 AM, MB Software Solutions General Account
mbsoftwaresoluti...@mbsoftwaresolutions.com wrote:
Stephen Russell wrote:
On Mon, Feb 2, 2009 at 9:06 AM, Charlie Coleman colem...@acm.org wrote:
ROFL. Where have you been? The viruses are all still around, popping in
You're more than welcome, Vince.
On Sun, Feb 1, 2009 at 7:48 AM, Vince Teachout tea...@taconic.net wrote:
Grigore Dolghin wrote:
Here is a innosetup script which deals with everything regarding
installing
a visual foxpro application under vista
Grigore,
Thank you very much for this. I
...@leafe.com
Subject: VFP 9 runtime on Vista, the QD way
I've been asked to do a qd install of an upgrade for a vertical app.
The upgrade is going to consist of:
1. Running a VFP .APP from within the existing system to upgrade the
data structures.
2. Installing a new EXE (VFP9)
3
It isn't always the developer's choice. In my experience, some clients
will insist on the app being installed on the network file server, while
others will insist on it being installed on each local workstation. So,
it's good to have a strategy for each type of deployment.
Agreed that it's
Hi Vince
Remember that talk about a loader program ?
Well I got a setup just like that, I only update the server and
the loader takes cares of updating the stations.
I had to twist a little because I have different data, depending
on the shop and a shop can have many stations.
HTH, Eurico.
Vince Teachout wrote:
Rick Borup wrote:
[MB wrote:]
...what's a good reason for the client to absolutely insist that
the program be installed on the LAN instead of the local machine?
Ease of updates. I have a client with several workstations, so if the
software is installed locally, he has
MB Software Solutions General Account wrote:
An absolutely perfect reason.why you should have a loader!!
Otherwise, I'd agree! ;-)
I don't believe you've had the pleasure of meeting this client yet.
But don't worry, the subject of dashboards came up, and you soon will!
Then we'll
Eurico Chagas Filho wrote:
Hi Vince
Remember that talk about a loader program ?
Well I got a setup just like that, I only update the server and
the loader takes cares of updating the stations.
I had to twist a little because I have different data, depending
on the shop and a shop can have
Rick Schummer wrote:
but what's a good reason for the client to absolutely insist that the
program be installed on the
LAN instead of the local machine?
- IT Standards for the organization
Can't argue with that, but have you really ever seen Microsoft Office installed
and
running from
Vince Teachout wrote:
Rick Borup wrote:
[MB wrote:]
...what's a good reason for the client to absolutely insist that
the program be installed on the LAN instead of the local machine?
Ease of updates. I have a client with several workstations, so if the
software is installed locally, he
Vince Teachout wrote:
Eurico Chagas Filho wrote:
Hi Vince
Remember that talk about a loader program ?
Well I got a setup just like that, I only update the server and
the loader takes cares of updating the stations.
I had to twist a little because I have different data, depending
on the
Paul McNett wrote:
You need to allow the domain users read, write, and execute permission on the
updatable exe file. Is that such a bad compromise?
With the particular client, it might be. He wasn't interested in web
update, because he couldn't control it. IOW, this is one of those
Paul,
Can't argue with that, but have you really ever seen Microsoft Office
installed and
running from the network?
Yes, probably the exact same performance you would get with any app designed to
work on a local
workstation. I am guessing the same with Open Office for similar reasons wink.
Rick Schummer wrote:
Paul,
Can't argue with that, but have you really ever seen Microsoft Office
installed and
running from the network?
Yes, probably the exact same performance you would get with any app designed
to work on a local
workstation. I am guessing the same with Open
Here is a innosetup script which deals with everything regarding installing
a visual foxpro application under vista, in program files. UAC is taken care
off, the visual foxpro runtime is installed silently in the correct location
and correctly registered, also mysql odbc driver is installed. VFP
Account
To: ProFox Email List
Sent: Friday, January 30, 2009 12:39 PM
Subject: RE: VFP 9 runtime on Vista, the QD way
On Fri, January 30, 2009 2:35 pm, Rick Borup wrote:
[Paul wrote:]
Oh but why install the app on the network drive? IMO apps
should be installed on the local computer. I realize
On Fri, Jan 30, 2009 at 3:01 PM, KAM.covad
a_gmail_nos...@kenmcginnis.com wrote:
Installing on the local machine will not work for my clients. I have tried
it. It is a mess. If you have 8 workstations, you would have to update all 8
at the same time. You would have to deal with that stupid MS
Grigore Dolghin wrote:
Here is a innosetup script which deals with everything regarding installing
a visual foxpro application under vista
Grigore,
Thank you very much for this. I am in the process of setting up an inno
script for one of my Apps, and this will help very much. Thank you!
...@leafe.com] On
Behalf Of Whil Hentzen
Sent: Thursday, January 29, 2009 06:25 PM
To: profoxt...@leafe.com
Subject: VFP 9 runtime on Vista, the QD way
I've been asked to do a qd install of an upgrade for a vertical app.
The upgrade is going to consist of:
1. Running a VFP .APP from within
At 05:24 PM 1/29/2009 -0600, Whil Hentzen wrote:
I've been asked to do a qd install of an upgrade for a vertical app.
The upgrade is going to consist of:
Vista lessons learned:
For one, never install anything under \program files\ (unless MS gets their
head out of their butt and allows
Rick Schummer wrote:
Hi Whil,
Runtimes for VFP absolutely do not go in the Windows System folder. Practice
of using the System
folder and associated DLL Hell has been frowned upon for years. If they are
put 'where they belong'
(or the standard folder) you would install them to:
[Paul wrote:]
Oh but why install the app on the network drive? IMO apps
should be installed on the local computer. I realize this
is an old, old argument around here, too.
It isn't always the developer's choice. In my experience, some clients will
insist on the app being installed on the
Oh but why install the app on the network drive? IMO apps should be
installed on the local
computer. I realize this is an old, old argument around here, too.
I was not recommending it be on a network, and I doubt Whil's question related
to Vista was
installing it on a network. It seems
On Fri, January 30, 2009 2:35 pm, Rick Borup wrote:
[Paul wrote:]
Oh but why install the app on the network drive? IMO apps
should be installed on the local computer. I realize this is an old, old
argument around here, too.
It isn't always the developer's choice. In my experience, some
but what's a good reason for the client to absolutely insist that the
program be installed on the
LAN instead of the local machine?
- IT Standards for the organization
- Absolutely guarantees everyone will run the same EXE (no local copies on
workstation with previous
bugs because launcher
[MB wrote:]
...what's a good reason for the client to absolutely insist that
the program be installed on the LAN instead of the local machine?
RAS's answer pretty much covers it. For example, I have a client who likes
to keep his workstations as pristine as possible, with nothing installed
Rick Borup wrote:
[MB wrote:]
...what's a good reason for the client to absolutely insist that
the program be installed on the LAN instead of the local machine?
Ease of updates. I have a client with several workstations, so if the
software is installed locally, he has to go to many
I've been asked to do a qd install of an upgrade for a vertical app.
The upgrade is going to consist of:
1. Running a VFP .APP from within the existing system to upgrade the
data structures.
2. Installing a new EXE (VFP9)
3. Installing the VFP 9 runtimes.
Given the structure of the system,
Whil Hentzen wrote:
1. Put the runtimes in the PF folder along with the EXE. This is the QD
mechanism...
This is what I would do. And note that the user will still not have write
access
here. If you want the user to be able to install your app without administrator
access, you can install
On Thu, Jan 29, 2009 at 5:24 PM, Whil Hentzen
list...@softwaremuscle.com wrote:
I've been asked to do a qd install of an upgrade for a vertical app.
The upgrade is going to consist of:
1. Running a VFP .APP from within the existing system to upgrade the
data structures.
2. Installing a new
Stephen Russell wrote:
Run times belong where you stated. Not data. They call the folder
Program files don't they?
Whil didn't say *anything* about location of data files. He was asking about
*runtime
files*.
Last point is Admin rights for install. Business is heads up on this
already.
Paul McNett wrote:
Last point is Admin rights for install. Business is heads up on this
already. If they enforce a policy they have a staff for you to deal
with. The flip side is everyone is an Admin and we all know that
ain't right don't we?
The installer should provide a default
easies is to get the runtimes from Ed's site install. VFP will find and
use
Richard E. Quilhot C.N.A.
quilh...@gmail.com
Bill Cosby - A word to the wise ain't necessary - it's the stupid ones
that need the advice.
On Thu, Jan 29, 2009 at 6:59 PM, Paul McNett p...@ulmcnett.com wrote:
51 matches
Mail list logo
