> 2. Re: Tables in the Data Enviroment
> Message: 2
> Date: Wed, 2 Apr 2008 15:39:24 -0400 (EDT)
> From: "MB Software Solutions General Account"
> <[EMAIL PROTECTED]>
> Subject: Re: Tables in the Data Enviroment
> To: [EMAIL PROTECTED]
> Message-ID: <[EMAIL PROTECTED]>
> Content-Type: text/plain; charset="us-ascii"
>
> Gil Hale wrote:
> >> Having the form on the server (or in an EXE) is not as efficient as you
> >>
> > might
> >
> >> think. The form or exe is not copied to the PC, it is accessed
> >> repeatedly.
> >>
> >
> > I ran into this back in my floundering VFP3 days, when I did not know any
> > better. I was told to create a formset that could be updated once on the
> > Server so all users would see the newest version of a very data intensive
> > application. So, I compiled the project as an .exe to be fired from the
> > Server as directed (my gut told me it would be a problem, but what did I
> > know?) My first indication that something was wrong was when I was doing
> > some training and one of my colleagues challenged the students to all load
> > the app at the same time, with the .exe running on a P75 Server with 64Mg
> > RAM! CRASH!!! Never challenge anyone to do anything that has not been
> > thoroughly tested first <g>... ("Uh, Dave, that is not a good idea...
> > Okay, you'll see..." <g>...)
> >
> > Anyway, the forms would take a long time to load into local RAM, about 1.5
> > minutes on a 100BaeTx connection, even with a single user hitting it. Once
> > I broke away onto my own, and put together my own VFP creations I began to
> > use all forms and form sets on the local PC (compiled as .exe files of
> > course). To get updated .app files onto the local PCs I used a
> technique Ed
> > put togther (available for free, but I can't recall where in his
> archives it
> > is. It is called "launcher"). Launcher is compiled as an .exe file,
> and it
> > compares a local .app to a version on the Server. If the Server version is
> > newer it copies it locally. Once it is happy that the local PC has the
> > latest compiled .app it fires it off and away we go. No more Server based
> > forms and formsets to keep all users current, no more manual
> > uninstall/reinstall with new versions, and no more manual copy from Server
> > routines. Quick, dirty and simple.
> >
>
> I had put a LOADER utility up there for this purpose.
Call it what you will, but I think a user double clicking a desktop
icon is called launching an application. These utilities copy/load
newer files/exes to the local pc and/or launch the local exe.
I think a Fox exe is something of a loader/launcher too. Components
from the exe are launched over and over as the user summons them. The
entire exe is not copied to the local pc unless we use a
loader/launcher. Frankly I find it hard to imagine a situation where
the local exe could result in slower operation than a remote exe on a
server.
:)
Mike Yearwood
_______________________________________________
Post Messages to: [email protected]
Subscription Maintenance: http://leafe.com/mailman/listinfo/profox
OT-free version of this list: http://leafe.com/mailman/listinfo/profoxtech
Searchable Archive: http://leafe.com/archives/search/profox
This message: http://leafe.com/archives/byMID/profox/[EMAIL PROTECTED]
** All postings, unless explicitly stated otherwise, are the opinions of the
author, and do not constitute legal or medical advice. This statement is added
to the messages for those lawyers who are too stupid to see the obvious.
