Re: [NF] Microsoft wrongly blocking lots of emails
I think the problems started after 25 Dec but could be wrong. I'd throw a few bucks on the "I bet you're right" square. ;-) Still no solution from M$ yet...7 days later. That's absolutely INSANE. The Planet's LARGEST IT COMPANY (or damn near) and this still isn't resolved. My IT guy says he's been dealing with several not-very-good-at-all-speaking-English persons and it seems like each time he has to start over...their communication skills are abysmal. Don't you love this global village? On 1/6/2022 11:25 AM, Man-wai Chang wrote: Could it be the Microso$t Exchange bug that was triggered on 01 Jan 2022? On Thu, Jan 6, 2022 at 4:28 AM MB Software Solutions, LLC wrote: Anybody else experiencing errors like this trying to email folks who use Office 365 as their email provider? Access denied, banned sender[172.104.208.100]. To request removal from this list please forward this message todel...@messaging.microsoft.com. For more information please go to http://go.microsoft.com/fwlink/?LinkId=526653. AS(1410) [BN1NAM02FT015.eop-nam02.prod.protection.outlook.com] (in reply to RCPT TO command) [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/f7eee44b-373e-1772-603a-5a484d8ae...@mbsoftwaresolutions.com ** 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.
RE: Problem trying to run a Powershell script as an Explorer shell command (Fox related)
Searching for ".pjx" in the registry gives the following:
Computer\HKEY_CLASSES_ROOT\.pjx (Default) REG_SZ
Visual.FoxPro.Project
Computer\HKEY_CURRENT_USER\Software\Microsoft\Windows\CurrentVersion\Explore
r\FileExts\.PJX\OpenWithList(Default) REG_SZ (value not
set)
Computer\HKEY_CURRENT_USER\Software\Microsoft\Windows\CurrentVersion\Explore
r\FileExts\.PJX\OpenWithLista REG_SZ vfp9.exe
Computer\HKEY_CURRENT_USER\Software\Microsoft\Windows\CurrentVersion\Explore
r\FileExts\.PJX\OpenWithListMRUList REG_SZ a
Computer\HKEY_CURRENT_USER\Software\Microsoft\Windows\CurrentVersion\Explore
r\FileExts\.PJX\OpenWithProgids (Default) REG_SZ (value not set)
Computer\HKEY_CURRENT_USER\Software\Microsoft\Windows\CurrentVersion\Explore
r\FileExts\.PJX\OpenWithProgids Visaul.FoxPro.Project REG_NONE
(zero-length binary value)
Computer\HKEY_LOCAL_MACHINE\SOFTWARE\Classes\.pjx (Default)
REG_SZ Visual.FoxPro.Project
Mike
-Original Message-
From: ProfoxTech [mailto:profoxtech-boun...@leafe.com] On Behalf Of
paul.newton.h...@gmail.com
Sent: Friday, January 07, 2022 4:57 PM
To: profoxt...@leafe.com
Subject: RE: Problem trying to run a Powershell script as an Explorer shell
command (Fox related)
Hi Mike
Could you show us what relevant entries you have in the registry - for as
long as I can remember double clicking on a PJX gives ... not an object file
Paul
Off to bed until tomorrow
-Original Message-
From: ProfoxTech On Behalf Of Michael
Glassman
Sent: 07 January 2022 23:52
To: profoxt...@leafe.com
Subject: RE: Problem trying to run a Powershell script as an Explorer shell
command (Fox related)
Paul,
I'm not sure why you're having to go to such lengths. When I double-click a
PJX or PJT file in Windows Explorer, the project automatically opens up in
the project manager.
Mike
-Original Message-
From: ProfoxTech [mailto:profoxtech-boun...@leafe.com] On Behalf Of
paul.newton.h...@gmail.com
Sent: Friday, January 07, 2022 3:43 PM
To: profoxt...@leafe.com
Subject: Problem trying to run a Powershell script as an Explorer shell
command (Fox related)
Hi all
I have been toying on and off over several years with a method of opening
VFP with a MODIFY command when double-clicking a file in Explorer. For
example, double-clicking on a PJX in Explorer should open VFP with the
command MODIFY PROJECT NOWAIT.
I am almost there, maybe. At the moment everything is in C:\Temp
ConFig.FPW contains
Command = C:\Temp\FoxOpen.PRG
*FoxOpen.PRG is constructed on-the fly by a PowerShell script TEST.PS1 as
follows:
TEST.PS1
Param([string]$a)
$file=Get-Item "$a"
$Extension = $file.Extension.ToUpper()
$Command = ""
switch ($Extension)
{
.PJX
{
$Command = "Modify Project '"+ $a + "' NOWAIT"
}
# Other cases follow
}
Set-Content -Path C:\Temp\FoxOpen.PRG -Value $Command
& "C:\Program Files (x86)\Microsoft Visual FoxPro 9\vfp9.exe"
-CC:\Temp\Config.FPW
I have tested this in a PowerShell console like this
PS C:\Temp> C:\Temp\Test.PS1 where is a fully qualified
path to a PJX, enclosed in single quotes
I have also tested in a COMMAND window like this
C:\Temp> PowerShell C:\Temp\Test.PS1 again where is a
fully qualified path to a PJX, enclosed in single quotes
So far, so good. Now for how to implement the shell command. My registry
settings are as follows:
Computer\HKEY_CLASSES_ROOT
PJXFile (Default) REG-SZ Project (FoxPro)
Shell (Default) REG_SZ (value not set)
Modify project (Default) REG_SZ (value not
set)
Command (Default)
REG_SZ "POWERSHELL C:\Temp\Test1.PS1" "%1"
However, double-clicking on a PJX results in:
Windows cannot access the specified device, path or file. You may not have
the appropriate permissions to access the item.
It seems as if I am nearly there, so any suggestions will be very gratefully
received. Many thanks
Paul Newton
P.S. My first attempt at doing anything useful with PowerShell
--- 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/02ec01d80426$c69d5e20$53d81a60$@PioneerDrama.com
** 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
RE: Problem trying to run a Powershell script as an Explorer shell command (Fox related)
Hi Mike
Could you show us what relevant entries you have in the registry - for as
long as I can remember double clicking on a PJX gives ... not an object file
Paul
Off to bed until tomorrow
-Original Message-
From: ProfoxTech On Behalf Of Michael
Glassman
Sent: 07 January 2022 23:52
To: profoxt...@leafe.com
Subject: RE: Problem trying to run a Powershell script as an Explorer shell
command (Fox related)
Paul,
I'm not sure why you're having to go to such lengths. When I double-click a
PJX or PJT file in Windows Explorer, the project automatically opens up in
the project manager.
Mike
-Original Message-
From: ProfoxTech [mailto:profoxtech-boun...@leafe.com] On Behalf Of
paul.newton.h...@gmail.com
Sent: Friday, January 07, 2022 3:43 PM
To: profoxt...@leafe.com
Subject: Problem trying to run a Powershell script as an Explorer shell
command (Fox related)
Hi all
I have been toying on and off over several years with a method of opening
VFP with a MODIFY command when double-clicking a file in Explorer. For
example, double-clicking on a PJX in Explorer should open VFP with the
command MODIFY PROJECT NOWAIT.
I am almost there, maybe. At the moment everything is in C:\Temp
ConFig.FPW contains
Command = C:\Temp\FoxOpen.PRG
*FoxOpen.PRG is constructed on-the fly by a PowerShell script TEST.PS1 as
follows:
TEST.PS1
Param([string]$a)
$file=Get-Item "$a"
$Extension = $file.Extension.ToUpper()
$Command = ""
switch ($Extension)
{
.PJX
{
$Command = "Modify Project '"+ $a + "' NOWAIT"
}
# Other cases follow
}
Set-Content -Path C:\Temp\FoxOpen.PRG -Value $Command
& "C:\Program Files (x86)\Microsoft Visual FoxPro 9\vfp9.exe"
-CC:\Temp\Config.FPW
I have tested this in a PowerShell console like this
PS C:\Temp> C:\Temp\Test.PS1 where is a fully qualified
path to a PJX, enclosed in single quotes
I have also tested in a COMMAND window like this
C:\Temp> PowerShell C:\Temp\Test.PS1 again where is a
fully qualified path to a PJX, enclosed in single quotes
So far, so good. Now for how to implement the shell command. My registry
settings are as follows:
Computer\HKEY_CLASSES_ROOT
PJXFile (Default) REG-SZ Project (FoxPro)
Shell (Default) REG_SZ (value not set)
Modify project (Default) REG_SZ (value not
set)
Command (Default)
REG_SZ "POWERSHELL C:\Temp\Test1.PS1" "%1"
However, double-clicking on a PJX results in:
Windows cannot access the specified device, path or file. You may not have
the appropriate permissions to access the item.
It seems as if I am nearly there, so any suggestions will be very gratefully
received. Many thanks
Paul Newton
P.S. My first attempt at doing anything useful with PowerShell
--- 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/016101d80422$39a3e0b0$aceba210$@gmail.com
** 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.
RE: Problem trying to run a Powershell script as an Explorer shell command (Fox related)
Paul,
I'm not sure why you're having to go to such lengths. When I double-click a
PJX or PJT file in Windows Explorer, the project automatically opens up in
the project manager.
Mike
-Original Message-
From: ProfoxTech [mailto:profoxtech-boun...@leafe.com] On Behalf Of
paul.newton.h...@gmail.com
Sent: Friday, January 07, 2022 3:43 PM
To: profoxt...@leafe.com
Subject: Problem trying to run a Powershell script as an Explorer shell
command (Fox related)
Hi all
I have been toying on and off over several years with a method of opening
VFP with a MODIFY command when double-clicking a file in Explorer. For
example, double-clicking on a PJX in Explorer should open VFP with the
command MODIFY PROJECT NOWAIT.
I am almost there, maybe. At the moment everything is in C:\Temp
ConFig.FPW contains
Command = C:\Temp\FoxOpen.PRG
*FoxOpen.PRG is constructed on-the fly by a PowerShell script TEST.PS1 as
follows:
TEST.PS1
Param([string]$a)
$file=Get-Item "$a"
$Extension = $file.Extension.ToUpper()
$Command = ""
switch ($Extension)
{
.PJX
{
$Command = "Modify Project '"+ $a + "' NOWAIT"
}
# Other cases follow
}
Set-Content -Path C:\Temp\FoxOpen.PRG -Value $Command
& "C:\Program Files (x86)\Microsoft Visual FoxPro 9\vfp9.exe"
-CC:\Temp\Config.FPW
I have tested this in a PowerShell console like this
PS C:\Temp> C:\Temp\Test.PS1 where is a fully qualified
path to a PJX, enclosed in single quotes
I have also tested in a COMMAND window like this
C:\Temp> PowerShell C:\Temp\Test.PS1 again where is a
fully qualified path to a PJX, enclosed in single quotes
So far, so good. Now for how to implement the shell command. My registry
settings are as follows:
Computer\HKEY_CLASSES_ROOT
PJXFile (Default) REG-SZ Project (FoxPro)
Shell (Default) REG_SZ (value not set)
Modify project (Default) REG_SZ (value not
set)
Command (Default)
REG_SZ "POWERSHELL C:\Temp\Test1.PS1" "%1"
However, double-clicking on a PJX results in:
Windows cannot access the specified device, path or file. You may not have
the appropriate permissions to access the item.
It seems as if I am nearly there, so any suggestions will be very gratefully
received. Many thanks
Paul Newton
P.S. My first attempt at doing anything useful with PowerShell
--- 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/02e701d80421$97b4ccb0$c71e6610$@PioneerDrama.com
** 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.
RE: Problem trying to run a Powershell script as an Explorer shell command (Fox related)
Tracy
Tried several variations of quotes and spaces without success so far - will
have another look tomorrow. Thanks again
Paul
-Original Message-
From: ProfoxTech On Behalf Of Tracy Pearson
Sent: 07 January 2022 23:20
To: profoxt...@leafe.com
Subject: RE: Problem trying to run a Powershell script as an Explorer shell
command (Fox related)
Now it might be the quote marks and the parameters. Perhaps a single quote
mark.
"C:\Temp\Test1.PS1 '%1'"
Embedded quotes.
I'm grabbing at straws here.
The original entry was this:
"C:\Program Files (x86)\Microsoft Visual FoxPro 9\vfp9.exe" -SHELLOPEN "%1"
Me, I had created config.fpw files for each of my projects that have a
command entry to run a startup.prg that does my environment setup and opens
my project files.
I've not gotten myself into PowerShell. I'm so used to a command prompt from
the DOS days when we started Windows from a command.
HTH,
Tracy
-Original Message-
From: ProfoxTech [mailto:profoxtech-boun...@leafe.com] On Behalf Of
paul.newton.h...@gmail.com
Sent: Friday, January 07, 2022 6:10 PM
To: profoxt...@leafe.com
Subject: RE: Problem trying to run a Powershell script as an Explorer shell
command (Fox related)
Hi Tracy
I tried setting the command in the registry to
"C:\Windows\System32\WindowsPowerShell\v1.0\powershell.exe"
"C:\Temp\Test1.PS1" "%1"
I no longer get an error but all I see is a PowerShell window which flashes
on the screen briefly and then closes ...
Paul
-Original Message-
From: ProfoxTech On Behalf Of Tracy Pearson
Sent: 07 January 2022 22:55
To: profoxt...@leafe.com
Subject: RE: Problem trying to run a Powershell script as an Explorer shell
command (Fox related)
You may need the fully qualified path to the PowerShell executable for it to
work.
HTH,
Tracy
-Original Message-
From: ProfoxTech [mailto:profoxtech-boun...@leafe.com] On Behalf Of
paul.newton.h...@gmail.com
Sent: Friday, January 07, 2022 5:43 PM
To: profoxt...@leafe.com
Subject: Problem trying to run a Powershell script as an Explorer shell
command (Fox related)
Hi all
I have been toying on and off over several years with a method of opening
VFP with a MODIFY command when double-clicking a file in Explorer. For
example, double-clicking on a PJX in Explorer should open VFP with the
command MODIFY PROJECT NOWAIT.
I am almost there, maybe. At the moment everything is in C:\Temp
ConFig.FPW contains
Command = C:\Temp\FoxOpen.PRG
*FoxOpen.PRG is constructed on-the fly by a PowerShell script TEST.PS1 as
follows:
TEST.PS1
Param([string]$a)
$file=Get-Item "$a"
$Extension = $file.Extension.ToUpper()
$Command = ""
switch ($Extension)
{
.PJX
{
$Command = "Modify Project '"+ $a + "' NOWAIT"
}
# Other cases follow
}
Set-Content -Path C:\Temp\FoxOpen.PRG -Value $Command
& "C:\Program Files (x86)\Microsoft Visual FoxPro 9\vfp9.exe"
-CC:\Temp\Config.FPW
I have tested this in a PowerShell console like this
PS C:\Temp> C:\Temp\Test.PS1 where is a fully qualified
path to a PJX, enclosed in single quotes
I have also tested in a COMMAND window like this
C:\Temp> PowerShell C:\Temp\Test.PS1 again where is a
fully qualified path to a PJX, enclosed in single quotes
So far, so good. Now for how to implement the shell command. My registry
settings are as follows:
Computer\HKEY_CLASSES_ROOT
PJXFile (Default) REG-SZ Project (FoxPro)
Shell (Default) REG_SZ (value not set)
Modify project (Default) REG_SZ (value not
set)
Command (Default)
REG_SZ "POWERSHELL C:\Temp\Test1.PS1" "%1"
However, double-clicking on a PJX results in:
Windows cannot access the specified device, path or file. You may not have
the appropriate permissions to access the item.
It seems as if I am nearly there, so any suggestions will be very gratefully
received. Many thanks
Paul Newton
P.S. My first attempt at doing anything useful with PowerShell
--- 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/016001d8041e$834f6c60$89ee4520$@gmail.com
** 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.
RE: Problem trying to run a Powershell script as an Explorer shell command (Fox related)
Now it might be the quote marks and the parameters. Perhaps a single quote
mark.
"C:\Temp\Test1.PS1 '%1'"
Embedded quotes.
I'm grabbing at straws here.
The original entry was this:
"C:\Program Files (x86)\Microsoft Visual FoxPro 9\vfp9.exe" -SHELLOPEN "%1"
Me, I had created config.fpw files for each of my projects that have a
command entry to run a startup.prg that does my environment setup and opens
my project files.
I've not gotten myself into PowerShell. I'm so used to a command prompt from
the DOS days when we started Windows from a command.
HTH,
Tracy
-Original Message-
From: ProfoxTech [mailto:profoxtech-boun...@leafe.com] On Behalf Of
paul.newton.h...@gmail.com
Sent: Friday, January 07, 2022 6:10 PM
To: profoxt...@leafe.com
Subject: RE: Problem trying to run a Powershell script as an Explorer shell
command (Fox related)
Hi Tracy
I tried setting the command in the registry to
"C:\Windows\System32\WindowsPowerShell\v1.0\powershell.exe"
"C:\Temp\Test1.PS1" "%1"
I no longer get an error but all I see is a PowerShell window which flashes
on the screen briefly and then closes ...
Paul
-Original Message-
From: ProfoxTech On Behalf Of Tracy Pearson
Sent: 07 January 2022 22:55
To: profoxt...@leafe.com
Subject: RE: Problem trying to run a Powershell script as an Explorer shell
command (Fox related)
You may need the fully qualified path to the PowerShell executable for it to
work.
HTH,
Tracy
-Original Message-
From: ProfoxTech [mailto:profoxtech-boun...@leafe.com] On Behalf Of
paul.newton.h...@gmail.com
Sent: Friday, January 07, 2022 5:43 PM
To: profoxt...@leafe.com
Subject: Problem trying to run a Powershell script as an Explorer shell
command (Fox related)
Hi all
I have been toying on and off over several years with a method of opening
VFP with a MODIFY command when double-clicking a file in Explorer. For
example, double-clicking on a PJX in Explorer should open VFP with the
command MODIFY PROJECT NOWAIT.
I am almost there, maybe. At the moment everything is in C:\Temp
ConFig.FPW contains
Command = C:\Temp\FoxOpen.PRG
*FoxOpen.PRG is constructed on-the fly by a PowerShell script TEST.PS1 as
follows:
TEST.PS1
Param([string]$a)
$file=Get-Item "$a"
$Extension = $file.Extension.ToUpper()
$Command = ""
switch ($Extension)
{
.PJX
{
$Command = "Modify Project '"+ $a + "' NOWAIT"
}
# Other cases follow
}
Set-Content -Path C:\Temp\FoxOpen.PRG -Value $Command
& "C:\Program Files (x86)\Microsoft Visual FoxPro 9\vfp9.exe"
-CC:\Temp\Config.FPW
I have tested this in a PowerShell console like this
PS C:\Temp> C:\Temp\Test.PS1 where is a fully qualified
path to a PJX, enclosed in single quotes
I have also tested in a COMMAND window like this
C:\Temp> PowerShell C:\Temp\Test.PS1 again where is a
fully qualified path to a PJX, enclosed in single quotes
So far, so good. Now for how to implement the shell command. My registry
settings are as follows:
Computer\HKEY_CLASSES_ROOT
PJXFile (Default) REG-SZ Project (FoxPro)
Shell (Default) REG_SZ (value not set)
Modify project (Default) REG_SZ (value not
set)
Command (Default)
REG_SZ "POWERSHELL C:\Temp\Test1.PS1" "%1"
However, double-clicking on a PJX results in:
Windows cannot access the specified device, path or file. You may not have
the appropriate permissions to access the item.
It seems as if I am nearly there, so any suggestions will be very gratefully
received. Many thanks
Paul Newton
P.S. My first attempt at doing anything useful with PowerShell
--- 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/00f401d8041d$2206bfe0$66143fa0$@powerchurch.com
** 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.
RE: Problem trying to run a Powershell script as an Explorer shell command (Fox related)
Hi Tracy
I tried setting the command in the registry to
"C:\Windows\System32\WindowsPowerShell\v1.0\powershell.exe"
"C:\Temp\Test1.PS1" "%1"
I no longer get an error but all I see is a PowerShell window which flashes
on the screen briefly and then closes ...
Paul
-Original Message-
From: ProfoxTech On Behalf Of Tracy Pearson
Sent: 07 January 2022 22:55
To: profoxt...@leafe.com
Subject: RE: Problem trying to run a Powershell script as an Explorer shell
command (Fox related)
You may need the fully qualified path to the PowerShell executable for it to
work.
HTH,
Tracy
-Original Message-
From: ProfoxTech [mailto:profoxtech-boun...@leafe.com] On Behalf Of
paul.newton.h...@gmail.com
Sent: Friday, January 07, 2022 5:43 PM
To: profoxt...@leafe.com
Subject: Problem trying to run a Powershell script as an Explorer shell
command (Fox related)
Hi all
I have been toying on and off over several years with a method of opening
VFP with a MODIFY command when double-clicking a file in Explorer. For
example, double-clicking on a PJX in Explorer should open VFP with the
command MODIFY PROJECT NOWAIT.
I am almost there, maybe. At the moment everything is in C:\Temp
ConFig.FPW contains
Command = C:\Temp\FoxOpen.PRG
*FoxOpen.PRG is constructed on-the fly by a PowerShell script TEST.PS1 as
follows:
TEST.PS1
Param([string]$a)
$file=Get-Item "$a"
$Extension = $file.Extension.ToUpper()
$Command = ""
switch ($Extension)
{
.PJX
{
$Command = "Modify Project '"+ $a + "' NOWAIT"
}
# Other cases follow
}
Set-Content -Path C:\Temp\FoxOpen.PRG -Value $Command
& "C:\Program Files (x86)\Microsoft Visual FoxPro 9\vfp9.exe"
-CC:\Temp\Config.FPW
I have tested this in a PowerShell console like this
PS C:\Temp> C:\Temp\Test.PS1 where is a fully qualified
path to a PJX, enclosed in single quotes
I have also tested in a COMMAND window like this
C:\Temp> PowerShell C:\Temp\Test.PS1 again where is a
fully qualified path to a PJX, enclosed in single quotes
So far, so good. Now for how to implement the shell command. My registry
settings are as follows:
Computer\HKEY_CLASSES_ROOT
PJXFile (Default) REG-SZ Project (FoxPro)
Shell (Default) REG_SZ (value not set)
Modify project (Default) REG_SZ (value not
set)
Command (Default)
REG_SZ "POWERSHELL C:\Temp\Test1.PS1" "%1"
However, double-clicking on a PJX results in:
Windows cannot access the specified device, path or file. You may not have
the appropriate permissions to access the item.
It seems as if I am nearly there, so any suggestions will be very gratefully
received. Many thanks
Paul Newton
P.S. My first attempt at doing anything useful with PowerShell
--- 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/000901d8041b$bf801520$3e803f60$@gmail.com
** 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.
RE: Problem trying to run a Powershell script as an Explorer shell command (Fox related)
Thanks Tracy - I'll give that a try just now ... will let you know in a few
minutes
Paul
-Original Message-
From: ProfoxTech On Behalf Of Tracy Pearson
Sent: 07 January 2022 22:55
To: profoxt...@leafe.com
Subject: RE: Problem trying to run a Powershell script as an Explorer shell
command (Fox related)
You may need the fully qualified path to the PowerShell executable for it to
work.
HTH,
Tracy
-Original Message-
From: ProfoxTech [mailto:profoxtech-boun...@leafe.com] On Behalf Of
paul.newton.h...@gmail.com
Sent: Friday, January 07, 2022 5:43 PM
To: profoxt...@leafe.com
Subject: Problem trying to run a Powershell script as an Explorer shell
command (Fox related)
Hi all
I have been toying on and off over several years with a method of opening
VFP with a MODIFY command when double-clicking a file in Explorer. For
example, double-clicking on a PJX in Explorer should open VFP with the
command MODIFY PROJECT NOWAIT.
I am almost there, maybe. At the moment everything is in C:\Temp
ConFig.FPW contains
Command = C:\Temp\FoxOpen.PRG
*FoxOpen.PRG is constructed on-the fly by a PowerShell script TEST.PS1 as
follows:
TEST.PS1
Param([string]$a)
$file=Get-Item "$a"
$Extension = $file.Extension.ToUpper()
$Command = ""
switch ($Extension)
{
.PJX
{
$Command = "Modify Project '"+ $a + "' NOWAIT"
}
# Other cases follow
}
Set-Content -Path C:\Temp\FoxOpen.PRG -Value $Command
& "C:\Program Files (x86)\Microsoft Visual FoxPro 9\vfp9.exe"
-CC:\Temp\Config.FPW
I have tested this in a PowerShell console like this
PS C:\Temp> C:\Temp\Test.PS1 where is a fully qualified
path to a PJX, enclosed in single quotes
I have also tested in a COMMAND window like this
C:\Temp> PowerShell C:\Temp\Test.PS1 again where is a
fully qualified path to a PJX, enclosed in single quotes
So far, so good. Now for how to implement the shell command. My registry
settings are as follows:
Computer\HKEY_CLASSES_ROOT
PJXFile (Default) REG-SZ Project (FoxPro)
Shell (Default) REG_SZ (value not set)
Modify project (Default) REG_SZ (value not
set)
Command (Default)
REG_SZ "POWERSHELL C:\Temp\Test1.PS1" "%1"
However, double-clicking on a PJX results in:
Windows cannot access the specified device, path or file. You may not have
the appropriate permissions to access the item.
It seems as if I am nearly there, so any suggestions will be very gratefully
received. Many thanks
Paul Newton
P.S. My first attempt at doing anything useful with PowerShell
--- 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/015f01d80419$f0879320$d196b960$@gmail.com
** 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.
RE: Problem trying to run a Powershell script as an Explorer shell command (Fox related)
You may need the fully qualified path to the PowerShell executable for it to
work.
HTH,
Tracy
-Original Message-
From: ProfoxTech [mailto:profoxtech-boun...@leafe.com] On Behalf Of
paul.newton.h...@gmail.com
Sent: Friday, January 07, 2022 5:43 PM
To: profoxt...@leafe.com
Subject: Problem trying to run a Powershell script as an Explorer shell
command (Fox related)
Hi all
I have been toying on and off over several years with a method of opening
VFP with a MODIFY command when double-clicking a file in Explorer. For
example, double-clicking on a PJX in Explorer should open VFP with the
command MODIFY PROJECT NOWAIT.
I am almost there, maybe. At the moment everything is in C:\Temp
ConFig.FPW contains
Command = C:\Temp\FoxOpen.PRG
*FoxOpen.PRG is constructed on-the fly by a PowerShell script TEST.PS1 as
follows:
TEST.PS1
Param([string]$a)
$file=Get-Item "$a"
$Extension = $file.Extension.ToUpper()
$Command = ""
switch ($Extension)
{
.PJX
{
$Command = "Modify Project '"+ $a + "' NOWAIT"
}
# Other cases follow
}
Set-Content -Path C:\Temp\FoxOpen.PRG -Value $Command
& "C:\Program Files (x86)\Microsoft Visual FoxPro 9\vfp9.exe"
-CC:\Temp\Config.FPW
I have tested this in a PowerShell console like this
PS C:\Temp> C:\Temp\Test.PS1 where is a fully qualified
path to a PJX, enclosed in single quotes
I have also tested in a COMMAND window like this
C:\Temp> PowerShell C:\Temp\Test.PS1 again where is a
fully qualified path to a PJX, enclosed in single quotes
So far, so good. Now for how to implement the shell command. My registry
settings are as follows:
Computer\HKEY_CLASSES_ROOT
PJXFile (Default) REG-SZ Project (FoxPro)
Shell (Default) REG_SZ (value not set)
Modify project (Default)
REG_SZ (value not set)
Command (Default)
REG_SZ "POWERSHELL C:\Temp\Test1.PS1" "%1"
However, double-clicking on a PJX results in:
Windows cannot access the specified device, path or file. You may not have
the appropriate permissions to access the item.
It seems as if I am nearly there, so any suggestions will be very gratefully
received. Many thanks
Paul Newton
P.S. My first attempt at doing anything useful with PowerShell
--- 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/00f301d80419$a6587c60$f3097520$@powerchurch.com
** 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.
Problem trying to run a Powershell script as an Explorer shell command (Fox related)
Hi all
I have been toying on and off over several years with a method of opening
VFP with a MODIFY command when double-clicking a file in Explorer. For
example, double-clicking on a PJX in Explorer should open VFP with the
command MODIFY PROJECT NOWAIT.
I am almost there, maybe. At the moment everything is in C:\Temp
ConFig.FPW contains
Command = C:\Temp\FoxOpen.PRG
*FoxOpen.PRG is constructed on-the fly by a PowerShell script TEST.PS1 as
follows:
TEST.PS1
Param([string]$a)
$file=Get-Item "$a"
$Extension = $file.Extension.ToUpper()
$Command = ""
switch ($Extension)
{
.PJX
{
$Command = "Modify Project '"+ $a + "' NOWAIT"
}
# Other cases follow
}
Set-Content -Path C:\Temp\FoxOpen.PRG -Value $Command
& "C:\Program Files (x86)\Microsoft Visual FoxPro 9\vfp9.exe"
-CC:\Temp\Config.FPW
I have tested this in a PowerShell console like this
PS C:\Temp> C:\Temp\Test.PS1 where is a fully qualified
path to a PJX, enclosed in single quotes
I have also tested in a COMMAND window like this
C:\Temp> PowerShell C:\Temp\Test.PS1 again where is a
fully qualified path to a PJX, enclosed in single quotes
So far, so good. Now for how to implement the shell command. My registry
settings are as follows:
Computer\HKEY_CLASSES_ROOT
PJXFile (Default) REG-SZ Project (FoxPro)
Shell (Default) REG_SZ (value not set)
Modify project (Default)
REG_SZ (value not set)
Command (Default)
REG_SZ "POWERSHELL C:\Temp\Test1.PS1" "%1"
However, double-clicking on a PJX results in:
Windows cannot access the specified device, path or file. You may not have
the appropriate permissions to access the item.
It seems as if I am nearly there, so any suggestions will be very gratefully
received. Many thanks
Paul Newton
P.S. My first attempt at doing anything useful with PowerShell
--- StripMime Report -- processed MIME parts ---
multipart/alternative
text/plain (text body -- kept)
text/html
---
___
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/015501d80417$e0089f50$a019ddf0$@gmail.com
** 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.
RE: VFP9 and SQL memo fields - SOLVED
+1 John Weller 07976 393631 > -Original Message- > From: ProfoxTech On Behalf Of AndyHC > Sent: 07 January 2022 17:14 > To: profoxt...@leafe.com > Subject: Re: VFP9 and SQL memo fields - SOLVED > > On 06-Jan-22 7:54 AM, kbe...@mchsi.com wrote: > > So > > the cloud provider somehow talked the hackers into reducing the ransom to > $50,000 and they paid it 2 days after Christmas. > They should be prosecuted for paying it! - AndyD > > --- 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/02cc01d803ec$6cb731e0$462595a0$@johnweller.co.uk ** 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.
Re: VFP9 and SQL memo fields - SOLVED
On 06-Jan-22 7:54 AM, kbe...@mchsi.com wrote: So the cloud provider somehow talked the hackers into reducing the ransom to $50,000 and they paid it 2 days after Christmas. They should be prosecuted for paying it! - AndyD --- StripMime Report -- processed MIME parts --- multipart/alternative text/plain (text body -- kept) text/html --- ___ 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/626b5c7e-ae84-5b2a-277e-2b282b476...@hawthorncottage.com ** 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.
