SAPIEN Technologies

You don't say where in "globals" yo7u are defining these variables. They must be defined outside of any function.

Another good method is:

$global:Application = "System Tools"
$global:ApplicationVersion = "1.0.0"

$textbox1.Text = $global:Application

The ultimate outcome of all misadventures with computers is that, as dumb as they are, they always show us that humans are maters of dumb.

Good luck and may the force be with you -- or at least, not annoy you too much.

OR

$result = & $pathToScript\CALLEDSCRIPT.ps1 -Variable1 $var1 -Variable2 $var2

You still do not want the ampersand.

Invoke-Expression "$pathToScript\CALLEDSCRIPT.ps1 -Variable1 $var1 -Variable2 $var2"

You don't need quotes to call a PS1 script. YOu don't need to use&. $result = \\SERVER\PATH TO SCRIPT\CALLEDSCRIPT.ps1 -Variable1 $var1 -Variable2 $var2 If there are spaces in teh path then do this: $result = \\SERVER\'PATH TO SCRIPT'\CALLEDSCRIPT.ps1 -Variable1 $var1 -Variable2 $var2 Note the singl...

You also have to detect errors and decide what to do with them. You cannot use Invoke Command with a job. A job just takes a script block that contains the code to be executed. help start-job -online - read all of the help until you have a clear idea of how jobs work. You can also search for numero...

The answer is that you can't. A job runs in a s3eparte process and a session is process bound. You must connect separately in the job.

To do this you would have to enable auditing of the WSH engine (cscript, wscript). The audit records would then be available in the event log.

Hi Daniel Your issues are4 all a result of lack of knowledge of the basics of PowerShell. This wilkl make everything including how to use PSS very difficult. I recommend starting with a simple book to get you started. The first four chapters of this free and excellent introductory book will get you ...

https://docs.microsoft.com/en-us/dotnet ... ngRowIndex

$dataGridView1.FirstDisplayedScrollingRowIndex = $dataGridView1.SelectedRows[0].Index