Apologies, Vince:
The OT yellow card goes to Mr. MB Software Solutions, LLC for his
Consequences Culture reference, slipping into that all too slippery slope
of political culture wars and insurrection. Hie thee to OT, I say!
A thorough beating behind the woodshed, otoh, is a time-honored
I protest! Violent physical abuse of developers is a time-honored
tradition in the VFP community!
On 05/04/21 5:17 PM, Ted Roche wrote:
TWEET!!! Tweet! Off-Topic [OT]! 15 yard penalty, or a yellow card for out
other footballers.
On Tue, May 4, 2021 at 4:21 PM MB Software Solutions, LLC <
TWEET!!! Tweet! Off-Topic [OT]! 15 yard penalty, or a yellow card for out
other footballers.
On Tue, May 4, 2021 at 4:21 PM MB Software Solutions, LLC <
mbsoftwaresoluti...@mbsoftwaresolutions.com> wrote:
> On 5/4/2021 4:15 PM, Vince Teachout wrote:
> > Wow, it sounds like the remote developers
On 5/4/2021 4:15 PM, Vince Teachout wrote:
Wow, it sounds like the remote developers she works with are idiots.
I think she should grab them by their scrawny neck, and slam them
against the wall saying "Adhere TO CURRENT PROGRAMMING
PRACITICES OR I WILL END YOU! "
Careful,
On 05/04/21 3:53 PM, Ted Roche wrote:
Thanks for the insights, wOOdy! I recall installing VFP into its own
directories in the distant past, but I haven't done any clean installs on
new Windows machines in a long time. This was another developer's machine,
and she shares her project with other
I've never installed VFP in anything other than a folder named VFP(#) off the
root of my dev system C drive. Not for the cogent reasons w00dy mentions; just
because I thought it was totally unnecessary to install it anywhere else and
adding c:\vfp9 to my system path involved so much less
Thanks for the insights, wOOdy! I recall installing VFP into its own
directories in the distant past, but I haven't done any clean installs on
new Windows machines in a long time. This was another developer's machine,
and she shares her project with other remote developers and the project
files
As a rule of thumb: FoxPro as a Development system must not get installed in
%Program Files% ! That directory hive is only for Runtime apps, and such
those files are not allowed to write into that folders (Virus Prevention).
If they need to write program-specific files, those go into %Program
On 5/4/2021 9:31 AM, Frank Cazabon wrote:
Could it be anything to do with that old virtualisation thing that
Windows used to do?
Agreed...this sounds like the "sandbox" gotcha reported years ago.
--
This email has been checked for viruses by Avast antivirus software.
Tracy:
That did it. I renamed the files in the Virtual Store and everything
recompiles fine. What a time-saving feature the Virtual Store is!
THANK YOU!!!
On Tue, May 4, 2021 at 9:53 AM Ted Roche wrote:
> Tracy: I do find the files in the Virtual Store. What's the best way to
> fix, should I
Just a side note:
VFP A turns off the Virtualization that VFP 9 has.
I learned that when I was setting up FoxCodePlus to work in VFP A. It
doesn't work out of the box. And I type too fast for it. So I need to spend
some more time in the code. I have made notes in my forked repository.
I frequently just delete them when they corrupt there. The originals are
still in the protected place.
-Original Message-
From: ProfoxTech [mailto:profoxtech-boun...@leafe.com] On Behalf Of Ted
Roche
Sent: Tuesday, May 04, 2021 9:53 AM
To: profoxt...@leafe.com
Subject: Re: _framewk,vct
Tracy: I do find the files in the Virtual Store. What's the best way to
fix, should I delete them?
On Tue, May 4, 2021 at 9:52 AM Ted Roche wrote:
> I'm concerned that's solving a little problem with a big shotgun. This is
> a developer workstation that has been working okay for years, and a
I'm concerned that's solving a little problem with a big shotgun. This is a
developer workstation that has been working okay for years, and a set of
apps that do a lot of interprocess communication like Automation to Office,
and I don't want to create a bigger problem.
On Tue, May 4, 2021 at 9:31
Ted,
In the Windows Explorer there is a bar above the tree and file area that has
the path.
Click in the white space to the right and type the following
%localappdata%\VirtualStore\Program Files (x86)
You may find there is a "Micorsoft Visual FoxPro 9" folder there. It may
contain a corrupt
Grant the user (or everyone) full control?
Could it be anything to do with that old virtualisation thing that
Windows used to do?
Frank.
Frank Cazabon
On 04/05/2021 9:24 am, Ted Roche wrote:
Rebuilding a project that includes c:\program files (x86)\microsoft visual
foxpro
Rebuilding a project that includes c:\program files (x86)\microsoft visual
foxpro 9\wizards\_framewk.vcx gives the error
Memo file c:\program files (x86)\microsoft visual foxpro
9\wizards\_framewk.VCT is missing or invalid.
But it isn't and it's not.
I copied both _framewk files from another
VERY COOL, wOOdy How great that there's folks learning VFP yet. ;-)
I'll dig into this more later but at first try, this looks/works great.
An added bonus I wasn't seeing: setting the Team Captain ("Team X:
Name") from the grids as well including adding the guy to the group
(grid)
18 matches
Mail list logo
