Skip to main content

Use SAPIEN PowerShell Studio to protect your Nintendo Stock Gains

Thanks to a lot of press, Pokémon Go raised Nintendo’s stock price by over 30% Today.  Unfortunately, you may not be able to set a stop loss on it to protect those gains because it is traded on a foreign stock market.  In this post, we will use SAPIEN PowerShell Studio 2016 to create a small GUI to alert us should the stock fall below a specified price.


First off, create a New Form Project.


Next you will need to create a form using 3 labels and 2 text boxes. Set the name of the first text box to Textbox_Symbol and the second to Textbox_Low  for the fourth label, set the name to Label_Price.  The names of the other form controls do not matter for this exercise.

Pre-populate the value of Symbol with NTDOY.  Also pre-populate the value of Low with your selling price.

Also add a Timer control and leave the default settings.

In the script tab, replace the code with what is below.
$MainForm_Load={
  $timer1.Interval = 5000
       $timer1.Start()
}



$timer1_Tick={
       # Set the refresh for 5 minutes.
       $timer1.Interval = 300000
      
       function Get-StockInfo
       {
             
              $Sym = $textbox_Symbol.Text
              $URL = "http://finance.yahoo.com/d/quotes.csv?s=$Sym&f=snl1ghjk"
             
              $Obj = New-Object -TypeName PSObject -Property @{
                     Ask = $Null
                     DayLow = $Null
                     DayHigh = $Null
                     YearLow = $Null
                     YearHigh = $Null
              }
             
              $Data = Invoke-RestMethod -Uri $URL
              $Data = $Data.Replace("N/A", "NA")
              $Obj.Ask = ($Data.Split(","))[2]
              $Obj.DayLow = ($Data.Split(","))[3]
              $Obj.DayHigh = ($Data.Split(","))[4]
              $Obj.YearLow = ($Data.Split(","))[5]
              $Obj.YearHigh = ($Data.Split(","))[6]
             
              $label_Price.Text = $Obj.Ask
              If ($Obj.ask -gt $textbox_Low.text) {$label_Price.BackColor = 'Green'}
              Else { $label_Price.BackColor = 'Red'}
             
       } # END: function Get-StockInfo
      
       Get-StockInfo
}#end timer1_Tick


Here is the end result.

Not much, but if the price drops below $27.00, the price turns red.  This is just a basic example of how to create a GUI with SAPIEN PowerShell Studio 2016.  I encourage you to download the trial edition. You can down load it from here:

Remember that this is an alert from data that is about 10 to 20 minutes old.  You will also have to trigger the sell manually.  This is just a demo to show you the possibilities of using SAPIEN PowerShell Studio 2016 and not an actual stock trading tool.


Comments

Anonymous said…
Nice example, thanks! You can simplify the code by using CovertFrom-Csv for the custom object creation replacing 12 lines of code with:
$Obj = $Data.Replace("N/A","NA")|ConvertFrom-Csv -Header Symbol,Description,Ask,Daylow,DayHigh,YearLow,YearHigh

Popular posts from this blog

Sticky Key problem between Windows Server 2012 and LogMeIn

This week I instructed my first class using Windows Server 2012 accessed via LogMeIn and discovered a Sticky Key problem every time you press the Shift key. Here is my solution to resolve this.  First off, in the Preferences of LogMeIn for the connection to the Windows Server, click General . Change the Keyboard and mouse priority to Host side user and click Apply at the bottom. On the Windows 2012 server, open the Control Panel – Ease of Access – Change how your keyboard works . Uncheck Turn on Sticky Keys . Click Set up Sticky Keys . Uncheck Turn on Sticky Keys when SHIFT is pressed five times . Click OK twice. If you are using Windows Server 2012 as a Hyper-V host, you will need to redo the Easy of Use settings on each guest operating system in order to avoid the Sticky Key Problem. Updated Information: March 20, 2013 If you continue to have problems, Uncheck Turn on Filter Keys .

With the AD Recycle Bin Turned on, What Happens when you Create a User Account with a Password that does not meet the Password Policy?

This was an interesting observation from one of my Windows Server 2012 classes.  While working with the AD Recycle bin in a lab, one of my students discovered some interesting accounts that were created. When he created user accounts that did not meet password complexity requirements, an account is temporarily made and then deleted.  When a new password is provided that meets the password requirements, then a new account is made. We discovered this in two places.  First off in the Active Directory Administrative Center.  This is what caused the initial confusion.  Take a look.  This is in the Deleted Objects OU. You can see multiple deleted accounts for Test2 and one for Test3.  Test3 is a valid, functioning user account.  Using the PowerShell command Get-ADObject –IncludeDeletedObjects –Filter * –Properties ObjectSID we can see that indeed, two accounts were created, with one of them deleted. Notice the RID portion of the SID is different. ...

Where did a User’s Account Get Locked Out?

Updated: May 15, 2015 When this article was originally published, two extra carriage returns were add causing the code to malfunction.  The code below is correct.   My client for this week’s PowerShell class had a really interesting question. They needed to know where an account is being locked out at. OK, interesting. Apparently users hop around clients and forget to log off, leading to eventual lock out of their accounts. The accounts can be unlocked, but are then relocked after Active Directory replication. This problem is solved in two parts. The first one is to modify the event auditing on the network. The second part is resolved with PowerShell. The first part involves creating a group policy that will encompass your Domain Controllers. In this GPO, make these changes. Expand Computer Configuration \ Policies \ Windows Settings \ Security Settings \ Advanced Audit Policy Configuration \ Audit Policies \ Account Management Double click User Account Management C...