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 machine where it works, no change. I opened the file exclusively and tried to PACK and get the same error. I copy the two files to C:\temp and they pack fine, and compile classlib works there (after I also copied over _framewk.h) but moving the files back to the above directory and attempting a build project, rebuild all throws the same error.
This is a permissions issue with the program files (x86) folder and I've tried turning off the "Read Only" settings and in the folder permissions granting Modify and Write to the Users group, but the errors continue.
Any suggestions on how to get the Program files (x86) to be read-write for VFP? Moving the files to the project folder would be my preference, but it is not my project.
--- StripMime Report -- processed MIME parts --- multipart/alternative text/plain (text body -- kept) text/html ---
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 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 machine where it works, no change. I opened the file exclusively and tried to PACK and get the same error. I copy the two files to C:\temp and they pack fine, and compile classlib works there (after I also copied over _framewk.h) but moving the files back to the above directory and attempting a build project, rebuild all throws the same error.
This is a permissions issue with the program files (x86) folder and I've tried turning off the "Read Only" settings and in the folder permissions granting Modify and Write to the Users group, but the errors continue.
Any suggestions on how to get the Program files (x86) to be read-write for VFP? Moving the files to the project folder would be my preference, but it is not my project.
--- StripMime Report -- processed MIME parts --- multipart/alternative text/plain (text body -- kept) text/html
[excessive quoting removed by server]
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 AM Frank Cazabon frank.cazabon@gmail.com wrote:
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 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 machine where it works, no change. I opened the file exclusively and tried to PACK and get the same error. I copy the two files to C:\temp and they pack fine, and compile classlib works there (after I also copied over _framewk.h) but moving the files back to the above directory and attempting a build project, rebuild all throws the same error.
This is a permissions issue with the program files (x86) folder and I've tried turning off the "Read Only" settings and in the folder permissions granting Modify and Write to the Users group, but the errors continue.
Any suggestions on how to get the Program files (x86) to be read-write
for
VFP? Moving the files to the project folder would be my preference, but
it
is not my project.
--- StripMime Report -- processed MIME parts --- multipart/alternative text/plain (text body -- kept) text/html
[excessive quoting removed by server]
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 tedroche@gmail.com 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 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 AM Frank Cazabon frank.cazabon@gmail.com wrote:
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 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 machine where it works, no change. I opened the file exclusively and tried to PACK and get the same error. I copy the two files to C:\temp and they pack fine, and compile classlib works there (after I also copied over _framewk.h) but moving
the
files back to the above directory and attempting a build project,
rebuild
all throws the same error.
This is a permissions issue with the program files (x86) folder and I've tried turning off the "Read Only" settings and in the folder permissions granting Modify and Write to the Users group, but the errors continue.
Any suggestions on how to get the Program files (x86) to be read-write
for
VFP? Moving the files to the project folder would be my preference, but
it
is not my project.
--- StripMime Report -- processed MIME parts --- multipart/alternative text/plain (text body -- kept) text/html
[excessive quoting removed by server]
I frequently just delete them when they corrupt there. The originals are still in the protected place.
-----Original Message----- From: ProfoxTech [mailto:profoxtech-bounces@leafe.com] On Behalf Of Ted Roche Sent: Tuesday, May 04, 2021 9:53 AM To: profoxtech@leafe.com Subject: Re: _framewk,vct is missing or invalid, but it isn't and it's not.
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 tedroche@gmail.com 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 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 AM Frank Cazabon frank.cazabon@gmail.com wrote:
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 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 machine where it works, no change. I opened the file exclusively and tried to PACK and get the
same
error. I copy the two files to C:\temp and they pack fine, and compile classlib works there (after I also copied over _framewk.h) but moving
the
files back to the above directory and attempting a build project,
rebuild
all throws the same error.
This is a permissions issue with the program files (x86) folder and
I've
tried turning off the "Read Only" settings and in the folder
permissions
granting Modify and Write to the Users group, but the errors continue.
Any suggestions on how to get the Program files (x86) to be read-write
for
VFP? Moving the files to the project folder would be my preference, but
it
is not my project.
--- StripMime Report -- processed MIME parts --- multipart/alternative text/plain (text body -- kept) text/html
[excessive quoting removed by server]
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. https://github.com/Tracy-P/FoxcodePlus/blob/master/Installing_to_VFPA.md
-----Original Message----- From: ProfoxTech [mailto:profoxtech-bounces@leafe.com] On Behalf Of Ted Roche Sent: Tuesday, May 04, 2021 9:53 AM To: profoxtech@leafe.com Subject: Re: _framewk,vct is missing or invalid, but it isn't and it's not.
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 tedroche@gmail.com 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 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 AM Frank Cazabon frank.cazabon@gmail.com wrote:
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 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 machine where it works, no change. I opened the file exclusively and tried to PACK and get the
same
error. I copy the two files to C:\temp and they pack fine, and compile classlib works there (after I also copied over _framewk.h) but moving
the
files back to the above directory and attempting a build project,
rebuild
all throws the same error.
This is a permissions issue with the program files (x86) folder and
I've
tried turning off the "Read Only" settings and in the folder
permissions
granting Modify and Write to the Users group, but the errors continue.
Any suggestions on how to get the Program files (x86) to be read-write
for
VFP? Moving the files to the project folder would be my preference, but
it
is not my project.
--- StripMime Report -- processed MIME parts --- multipart/alternative text/plain (text body -- kept) text/html
[excessive quoting removed by server]
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 tedroche@gmail.com wrote:
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 tedroche@gmail.com 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 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 AM Frank Cazabon frank.cazabon@gmail.com wrote:
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 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 machine where it works, no change. I opened the file exclusively and tried to PACK and get the
same
error. I copy the two files to C:\temp and they pack fine, and compile classlib works there (after I also copied over _framewk.h) but moving
the
files back to the above directory and attempting a build project,
rebuild
all throws the same error.
This is a permissions issue with the program files (x86) folder and
I've
tried turning off the "Read Only" settings and in the folder
permissions
granting Modify and Write to the Users group, but the errors continue.
Any suggestions on how to get the Program files (x86) to be read-write
for
VFP? Moving the files to the project folder would be my preference,
but it
is not my project.
--- StripMime Report -- processed MIME parts --- multipart/alternative text/plain (text body -- kept) text/html
[excessive quoting removed by server]
On 5/4/2021 9:31 AM, Frank Cazabon wrote:
<snipped> 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.
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 _framewk.vcx.
HTH, Tracy
-----Original Message----- From: ProfoxTech [mailto:profoxtech-bounces@leafe.com] On Behalf Of Ted Roche Sent: Tuesday, May 04, 2021 9:25 AM To: profoxtech@leafe.com Subject: _framewk,vct is missing or invalid, but it isn't and it's not.
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 machine where it works, no change. I opened the file exclusively and tried to PACK and get the same error. I copy the two files to C:\temp and they pack fine, and compile classlib works there (after I also copied over _framewk.h) but moving the files back to the above directory and attempting a build project, rebuild all throws the same error.
This is a permissions issue with the program files (x86) folder and I've tried turning off the "Read Only" settings and in the folder permissions granting Modify and Write to the Users group, but the errors continue.
Any suggestions on how to get the Program files (x86) to be read-write for VFP? Moving the files to the project folder would be my preference, but it is not my project.
--- StripMime Report -- processed MIME parts --- multipart/alternative text/plain (text body -- kept) text/html ---
[excessive quoting removed by server]
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 Data%. And: that's a GOOD THING (tm)! If you insist to install under %program files%, you need to invoke all permissions on that folder. Since not all programs adhere to those principles, MS invented that VirtualStore, which is a really clever way to keep those stupid programs running and stil don't let viruses get into the secured area.
Unfortunately, FoxPro is too old for adhering to those Established Security Rules, that's why you should always install it to a different non-secured and non-supervised folder (like c:\Develop). See also http://woody-prolib.blogspot.com/ for installation of VFP9 in a modern world.
wOOdy
-----Ursprüngliche Nachricht----- Von: ProFox profox-bounces@leafe.com Im Auftrag von Ted Roche Gesendet: Dienstag, 4. Mai 2021 15:25 An: profox@leafe.com Betreff: _framewk,vct is missing or invalid, but it isn't and it's not.
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 machine where it works, no change. I opened the file exclusively and tried to PACK and get the same error. I copy the two files to C:\temp and they pack fine, and compile classlib works there (after I also copied over _framewk.h) but moving the files back to the above directory and attempting a build project, rebuild all throws the same error.
This is a permissions issue with the program files (x86) folder and I've tried turning off the "Read Only" settings and in the folder permissions granting Modify and Write to the Users group, but the errors continue.
Any suggestions on how to get the Program files (x86) to be read-write for VFP? Moving the files to the project folder would be my preference, but it is not my project.
--- StripMime Report -- processed MIME parts --- multipart/alternative text/plain (text body -- kept) text/html ---
[excessive quoting removed by server]
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 include paths of "c:\Program Files (x86)" and so forth, so changing them would be a pain in the... neck. But it's great info to know, and now I have some new techniques to debug weird problems.
I'd like to tell you that Linux is way easier than this, but it's just as inscrutable in its own way. Issues with SELinux or AppArmor security are just as obscure and difficult to troubleshoot.
Stupid computers :)
On Tue, May 4, 2021 at 3:10 PM Jürgen Wondzinski juergen@wondzinski.de wrote:
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 Data%. And: that's a GOOD THING (tm)! If you insist to install under %program files%, you need to invoke all permissions on that folder. Since not all programs adhere to those principles, MS invented that VirtualStore, which is a really clever way to keep those stupid programs running and stil don't let viruses get into the secured area.
Unfortunately, FoxPro is too old for adhering to those Established Security Rules, that's why you should always install it to a different non-secured and non-supervised folder (like c:\Develop). See also http://woody-prolib.blogspot.com/ for installation of VFP9 in a modern world.
wOOdy
-----Ursprüngliche Nachricht----- Von: ProFox profox-bounces@leafe.com Im Auftrag von Ted Roche Gesendet: Dienstag, 4. Mai 2021 15:25 An: profox@leafe.com Betreff: _framewk,vct is missing or invalid, but it isn't and it's not.
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 machine where it works, no change. I opened the file exclusively and tried to PACK and get the same error. I copy the two files to C:\temp and they pack fine, and compile classlib works there (after I also copied over _framewk.h) but moving the files back to the above directory and attempting a build project, rebuild all throws the same error.
This is a permissions issue with the program files (x86) folder and I've tried turning off the "Read Only" settings and in the folder permissions granting Modify and Write to the Users group, but the errors continue.
Any suggestions on how to get the Program files (x86) to be read-write for VFP? Moving the files to the project folder would be my preference, but it is not my project.
--- StripMime Report -- processed MIME parts --- multipart/alternative text/plain (text body -- kept) text/html
[excessive quoting removed by server]
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 typing.... You can pick up that folder and plop it down on ay other system and as long as you don't care about seeing it's registered to engineering prototype it's perfectly happy. And there are ways to get around that, too.
--
rk
-----Original Message----- From: ProfoxTech profoxtech-bounces@leafe.com On Behalf Of Ted Roche Sent: Tuesday, May 4, 2021 3:53 PM To: profoxtech@leafe.com Subject: Re: _framewk,vct is missing or invalid, but it isn't and it's not.
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 include paths of "c:\Program Files (x86)" and so forth, so changing them would be a pain in the... neck. But it's great info to know, and now I have some new techniques to debug weird problems.
I'd like to tell you that Linux is way easier than this, but it's just as inscrutable in its own way. Issues with SELinux or AppArmor security are just as obscure and difficult to troubleshoot.
Stupid computers :)
On Tue, May 4, 2021 at 3:10 PM Jürgen Wondzinski juergen@wondzinski.de wrote:
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 Data%. And: that's a GOOD THING (tm)! If you insist to install under %program files%, you need to invoke all permissions on that folder. Since not all programs adhere to those principles, MS invented that VirtualStore, which is a really clever way to keep those stupid programs running and stil don't let viruses get into the secured area.
Unfortunately, FoxPro is too old for adhering to those Established Security Rules, that's why you should always install it to a different non-secured and non-supervised folder (like c:\Develop). See also http://woody-prolib.blogspot.com/ for installation of VFP9 in a modern world.
wOOdy
-----Ursprüngliche Nachricht----- Von: ProFox profox-bounces@leafe.com Im Auftrag von Ted Roche Gesendet: Dienstag, 4. Mai 2021 15:25 An: profox@leafe.com Betreff: _framewk,vct is missing or invalid, but it isn't and it's not.
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 machine where it works, no change. I opened the file exclusively and tried to PACK and get the same error. I copy the two files to C:\temp and they pack fine, and compile classlib works there (after I also copied over _framewk.h) but moving the files back to the above directory and attempting a build project, rebuild all throws the same error.
This is a permissions issue with the program files (x86) folder and I've tried turning off the "Read Only" settings and in the folder permissions granting Modify and Write to the Users group, but the errors continue.
Any suggestions on how to get the Program files (x86) to be read-write for VFP? Moving the files to the project folder would be my preference, but it is not my project.
--- StripMime Report -- processed MIME parts --- multipart/alternative text/plain (text body -- kept) text/html
[excessive quoting removed by server]
_______________________________________________ Post Messages to: ProFox@leafe.com Subscription Maintenance: https://mail.leafe.com/mailman/listinfo/profox OT-free version of this list: https://mail.leafe.com/mailman/listinfo/profoxtech Searchable Archive: https://leafe.com/archives This message: https://leafe.com/archives/byMID/CACW6n4v6poLBxgZndenBog-O=_-jL12XtYMCADmGTE... ** 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. Report [OT] Abuse: http://leafe.com/reportAbuse/CACW6n4v6poLBxgZndenBog-O=_-jL12XtYMCADmGTEMtXi...
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 remote developers and the project files include paths of "c:\Program Files (x86)" and so forth, so changing them would be a pain in the... neck. But it's great info to know, and now I have some new techniques to debug weird problems.
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 <BANG!> TO CURRENT PROGRAMMING PRACITICES <BANG!><BANG!><BANG!> OR I WILL END YOU! <BANG!>"
Just a suggestion.
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 <BANG!> TO CURRENT PROGRAMMING PRACITICES <BANG!><BANG!><BANG!> OR I WILL END YOU! <BANG!>"
Careful, Vince....they'll cancel you. <gd&rvvf>
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 < mbsoftwaresolutions@mbsoftwaresolutions.com> wrote:
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 <BANG!> TO CURRENT PROGRAMMING PRACITICES <BANG!><BANG!><BANG!> OR I WILL END YOU! <BANG!>"
Careful, Vince....they'll cancel you. <gd&rvvf>
-- Michael J. Babcock, MCP Fox/VFP dev since 1997 Developer of FabNet estimating software - mbsoftwaresolutions.com
[excessive quoting removed by server]
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 < mbsoftwaresolutions@mbsoftwaresolutions.com> wrote:
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 <BANG!> TO CURRENT PROGRAMMING PRACITICES <BANG!><BANG!><BANG!> OR I WILL END YOU! <BANG!>"
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 tradition, I agree.
On Tue, May 4, 2021 at 5:22 PM Vince Teachout vinny@caracal.net wrote:
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 < mbsoftwaresolutions@mbsoftwaresolutions.com> wrote:
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 <BANG!> TO CURRENT PROGRAMMING PRACITICES <BANG!><BANG!><BANG!> OR I WILL END YOU! <BANG!>"
-- This email has been checked for viruses by Avast antivirus software. https://www.avast.com/antivirus
--- StripMime Report -- processed MIME parts --- multipart/alternative text/plain (text body -- kept) text/html ---
-
Frank Cazabon -
Jürgen Wondzinski -
MB Software Solutions, LLC -
Richard Kaye -
Ted Roche -
Tracy Pearson -
Vince Teachout