Kit Menke's Blog

Editing in SharePoint’s SPGridView

Kit — Fri, 19 Feb 2010 03:36:28 +0000

The goal of this post is to provide an easy to understand example of how to enable editing in an SPGridView. In this case, my datasource of choice is a SharePoint list.

The way that I chose to implement editing in an SPGridView involved two classes:

SimpleLogic – handles query and update operations
SimpleSPGrid – handles all of the setup for the ObjectDataSource and the SPGridView

The main advantage for splitting the two classes is to separate all of the business logic into one class. Ideally, you should be able to completely change how the SimpleLogic class retrieves/updates data without changing the SimpleSPGrid code.

The Setup

In this example, our logic class is retrieving and updating data in a SharePoint list. My SharePoint list had three main columns: Title (text), Region (choice), and Total Sales (currency).

Now that I had some data to read from and write to, I was ready to create my logic class.

The SimpleLogic Class

The goal for the logic class was to expose all of the operations the gridview would need in order to read or update data:

public DataTable Select()
How do I get the data?
public List GetColumns()
How do I display the data?
public void Update(Dictionary data)
How do I update the data?

public class SimpleLogic
{
    const string LIST_NAME = "Example Sales Data";
    readonly string[] LIST_COLUMNS = null;
    readonly string VIEW_FIELDS = string.Empty;
    readonly string[] DATA_KEY_NAMES = null;
    private SPWeb _currentWeb;
 
    public SimpleLogic(SPWeb currentWeb)
    {
        _currentWeb = currentWeb;
 
        DATA_KEY_NAMES = new string[1];
        DATA_KEY_NAMES[0] = "ID";
        LIST_COLUMNS = new string[4];
        LIST_COLUMNS[0] = "ID";
        LIST_COLUMNS[1] = "Title";
        LIST_COLUMNS[2] = "Region";
        LIST_COLUMNS[3] = "Total_x0020_Sales";
        VIEW_FIELDS = GetViewFields(LIST_COLUMNS);
    }
 
    public string[] GetDataKeyNames()
    {
        return DATA_KEY_NAMES;
    }
 
    public List<BoundField> GetColumns()
    {
        List<BoundField> fields = new List<BoundField>();
        fields.Add(GetBoundField("ID"));
        // we don't want the ID field to be editable so we make it readonly
        // readonly will mean a textbox to edit it will not be shown
        fields[0].ReadOnly = true;
        fields.Add(GetBoundField("Title"));
        fields.Add(GetBoundField("Region"));
        fields.Add(GetBoundField("Total_x0020_Sales"));
        return fields;
    }
 
    private BoundField GetBoundField(string name)
    {
        // do not use SPBoundField (will not work with editing)
        BoundField bf = new BoundField();
        bf.HeaderText = name;
        bf.DataField = name;
        return bf;
    }
 
    public DataTable Select()
    {
        SPQuery q = new SPQuery();
        q.ViewFields = VIEW_FIELDS;
        q.Query = "";
        SPList list = _currentWeb.Lists[LIST_NAME];
        SPListItemCollection items = list.GetItems(q);
        return items.GetDataTable();
    }
 
    private string GetViewFields(string[] columns)
    {
        StringBuilder sb = new StringBuilder();
        foreach (string field in columns)
        {
            sb.AppendFormat("", field);
        }
        return sb.ToString();
    }
 
    public void Update(Dictionary<string, string> data)
    {
        SPList list = _currentWeb.Lists[LIST_NAME];
        int id = Int32.Parse(data["ID"]);
        SPListItem item = list.GetItemById(id);
        item["Title"] = data["Title"];
        item["Region"] = data["Region"];
        item["Total_x0020_Sales"] = data["Total_x0020_Sales"];
        item.Update();
    }
}

DISCLAIMER: When actually implementing the class above, you will probably need to add some sort of error handling. In order to provide a simpler example, the error handling has been omitted.

Once our logic class is functioning correctly, we can work on hooking it up to an SPGridView.

The SimpleSPGrid Class

The SimpleSPGrid class contains most of the guts that will probably be different to you. The first thing to notice is that it takes our SimpleLogic class as a parameter. This allows us to instantiate our logic class beforehand with any parameters that are needed, and then pass it into SimpleSPGrid to use.

public class SimpleSPGrid : CompositeControl
{
    private SimpleLogic _logic;
    private ObjectDataSource _gridDS;
    private SPGridView _grid;
 
    public SimpleSPGrid(SimpleLogic logic)
    {
        _logic = logic;
    }
 
    protected sealed override void CreateChildControls()
    {
        const string GRIDID = "grid";
        const string DATASOURCEID = "gridDS";
 
        _gridDS = new ObjectDataSource();
        _gridDS.ID = DATASOURCEID;
        _gridDS.TypeName = typeof(SimpleLogic).AssemblyQualifiedName;
        _gridDS.ObjectCreating += new ObjectDataSourceObjectEventHandler(gridDS_ObjectCreating);
        _gridDS.SelectMethod = "Select";
 
        // to handle updates from the grid
        _gridDS.UpdateMethod = "Update";
        _gridDS.Updating += new ObjectDataSourceMethodEventHandler(gridDS_Updating);
 
        this.Controls.Add(_gridDS);
 
        // create our grid
        _grid = new SPGridView();
        _grid.ID = GRIDID;
        _grid.DataSourceID = _gridDS.ID; // link the grid to the ObjectDataSource
        _grid.AutoGenerateColumns = false; // must be false
 
        // generally the primary key field(s)
        // these will be passed as an input parameter
        _grid.DataKeyNames = _logic.GetDataKeyNames();
 
        // add the column that will allow editing
        CommandField command = new CommandField();
        command.ShowEditButton = true;
        _grid.Columns.Add(command);
 
        // add all of the columns in the datatable to the grid
        // any column that is not readonly will be passed as an input parameter
        foreach (BoundField column in _logic.GetColumns())
        {
            _grid.Columns.Add(column);
        }
 
        this.Controls.Add(_grid);
    }
 
    /// 
    /// Consolidates all of the InputParameters (values from the grid)
    /// into one dictionary of values to send to the update method
    /// 
    void gridDS_Updating(object sender, ObjectDataSourceMethodEventArgs e)
    {
        Dictionary<string, string> data = new Dictionary<string, string>();
 
        foreach (DictionaryEntry entry in e.InputParameters)
        {
            string value = entry.Value == null ? null : entry.Value.ToString();
            data.Add(entry.Key.ToString(), value);
        }
 
        e.InputParameters.Clear();
        e.InputParameters.Add("data", data);
    }
 
    /// 
    /// When the ObjectDataSource is created, hook it up to the Logic class
    /// (so that it uses the Logic class to make the Select, Update... calls)
    /// 
    private void gridDS_ObjectCreating(object sender, ObjectDataSourceEventArgs e)
    {
        e.ObjectInstance = _logic;
    }
}

Wrap up

Now that all the hard work is done, we are ready to use the classes inside our web part. Inside the CreateChildControls of your webpart you would have the following code ( even though we have an SPWeb here, it should NOT be disposed):

protected override void CreateChildControls()
{
    SimpleLogic logic = new SimpleLogic(SPControl.GetContextWeb(Context));
    SimpleSPGrid grid = new SimpleSPGrid(logic);
    this.Controls.Add(grid);
}

This will produce the following grid!

And clicking edit…

Relative Dates in JavaScript

Kit — Sun, 24 Jan 2010 03:37:41 +0000

I was developing an input form for a search when I came across the need to allow the user to filter items using a date range. I had two input boxes where the user could enter a start and an end date. For some of the most common date ranges, I decided to create links that could be clicked to auto-populate the start/end date textboxes. For example, searching for items that were created last week or last month. Using JavaScript’s Date object, I was able to put together some nice examples.

First, the setup. I needed two text boxes to hold the start/end dates and then wanted the user to click links to auto-populate them with some relative dates:

<a href="javascript: void(0);" onclick="return setRelativeDate('today')">Today</a>
 
<label for="txtStartDate">Start Date:</label><input id="txtStartDate" type="text" />
<label for="txtEndDate">End Date:</label><input id="txtEndDate" type="text" />

Then to figure out how to calculate the dates using JavaScript. Here are the examples.. starting out easy with Today’s date. When creating a new Date object, it is automatically initialized to the current day and time:

var today = new Date();
txtStartDate.value = getShortDateString(today);
txtEndDate.value = txtStartDate.value;

Yesterday is Today -1:

var yesterday = new Date();
yesterday.setDate(yesterday.getDate()-1);
txtStartDate.value = getShortDateString(yesterday);
txtEndDate.value = txtStartDate.value;

This Week is a little more complicated. getDate() returns the day of the month (1-31) and getDay() returns the day of the week (0-6).

var thisWeek = new Date();
// set the date to most recent Sunday
thisWeek.setDate(thisWeek.getDate() - thisWeek.getDay());
txtStartDate.value = getShortDateString(thisWeek);
// set the date to last week's Saturday
thisWeek.setDate(thisWeek.getDate() + 6);
txtEndDate.value = getShortDateString(thisWeek);

Last Week is pretty similar to this week. I think the hardest part for me is the function names getDate and getDay. I always was getting them confused and thought that they should have been more specific… like getWeekDay and getMonthDay or something.

var lastWeek = new Date();
// set the date to last week's Sunday
lastWeek.setDate(lastWeek.getDate() - lastWeek.getDay() - 7);
txtStartDate.value = getShortDateString(lastWeek);
// set the date to last week's Saturday
lastWeek.setDate(lastWeek.getDate() + 6);
txtEndDate.value = getShortDateString(lastWeek);

The main difficulty I had with This Month was how to figure out the last day of the month. Luckily, if you can figure it out by selecting the first of next month and then subtracting a day.

var lastDayOfThisMonth = new Date();
// go to the next month
var nextMonth = lastDayOfThisMonth.getMonth() + 1;
lastDayOfThisMonth.setMonth(nextMonth);
// go to the last day of the previous month (this month)
lastDayOfThisMonth.setDate(0);
txtEndDate.value = getShortDateString(lastDayOfThisMonth);
lastDayOfThisMonth.setDate(1);
txtStartDate.value = getShortDateString(lastDayOfThisMonth);

Notice how Last Month is actually easier because you can simply move backwards a month.

var lastDayOfLastMonth = new Date(); // now
lastDayOfLastMonth.setDate(0); // last day of last month            
// set the end date first
txtEndDate.value = getShortDateString(lastDayOfLastMonth);
lastDayOfLastMonth.setDate(1);
txtStartDate.value = getShortDateString(lastDayOfLastMonth);

The only issue I had with This Year was I didn’t realize that setMonth(int) took a zero based month: 0 = January … 11 = December.

var lastDayOfThisYear = new Date();
lastDayOfThisYear.setMonth(11); // December
lastDayOfThisYear.setDate(31);
txtEndDate.value = getShortDateString(lastDayOfThisYear);
lastDayOfThisYear.setMonth(0); // January
lastDayOfThisYear.setDate(1);
txtStartDate.value = getShortDateString(lastDayOfThisYear);

Finally, to figure out Last Year I took advantage of the setFullYear(year,month,day) function to subtract one year.

var lastDayOfLastYear = new Date();
// -1 means last year
// 11 means December and there always is a 31st of december
var thisYear = lastDayOfLastYear.getFullYear();
lastDayOfLastYear.setFullYear(thisYear - 1, 11, 31);
txtEndDate.value = getShortDateString(lastDayOfLastYear);
lastDayOfLastYear.setMonth(0); // January
lastDayOfLastYear.setDate(1); // 1st
txtStartDate.value = getShortDateString(lastDayOfLastYear);

See all of it together in the complete demo.

References:

Turning SharePoint SPAuditEntry Update into Create

Kit — Fri, 22 Jan 2010 21:42:47 +0000

If you’ve done any work with SharePoint and SPAuditEntry, you may have noticed the distinct lack of Create event. Instead, two Update events are created which means some extra processing is required.

For example, after uploading “NewTxtFile.txt” into a document library inside one of my sites, the following Audit Entries showed up.

>
  >9a70a244-1baa-4229-84ac-3f06bccecc7f>
  >19ce9254-93bc-41ff-9da1-ba5e994bf1c1>
  >Document>
  >2>
  >sites/MySiteCollection/MySubsite/Documents/NewTxtFile.txt>
  >Url>
  >1/22/2010 9:17:06 PM>
  >Update>
  >SharePoint>
>
 
>
  >9a70a244-1baa-4229-84ac-3f06bccecc7f>
  >f332a82b-17d1-4c31-9726-5259769f2695>
  >List>
  >2>
  >sites/MySiteCollection/MySubsite/Documents>
  >Url>
  >1/22/2010 9:17:06 PM>
  >Update>
  >SharePoint>
  >NewTxtFile.txt>
>

Notice the “Occurred” DateTime properties are the same as well the Event. Also, one is an Update for the List and one is an Update for the Document. Using this information, you can then simplify the duplicate Update events into one Create event!

AllowUnsafeUpdates and ValidateFormDigest

Kit — Wed, 23 Dec 2009 16:34:41 +0000

Add this to the list of things every SharePoint developer should know (up there with disposing SPWebs and SPSites).

In general…

Don’t update SharePoint objects on a GET request
Call SPUtility.ValidateFormDigest() before anything on a POST request

Here are the two links to read:

Internal column names: Site Columns vs List Columns

Kit — Wed, 02 Dec 2009 21:02:32 +0000

Two identical custom lists with the same columns. The only difference is that one list has columns added using Site Columns and the other list had columns added directly to the list. The same? Not so much…

Steps to repro this issue:

Create a site column named “A,B-C/D” (single line of text or any other type)
Create a list named “Special Characters (Site)”
Add the Site Column “A,B-C/D” to your “Special Characters (Site)” list.
Create another list named “Special Characters (List)”
Create a column in “Special Characters (List)” named the same as your site column (“A,B-C/D”)

Results:

	Column Added Using Site Column	Column Created Directly in the List
Column Name	A,B-C/D	A,B-C/D
Internal Column Name	A_x002C_B_x002d_C_x002F_D	A_x002c_B_x002d_C_x002f_D

The internal column names are DIFFERENT.

… but only for some of the characters. Looks like the comma and the slash are different but not the dash.

Updating choice fields via SharePoint Web Services

Kit — Fri, 30 Oct 2009 16:06:40 +0000

My problem started with a simple change to a site column. I had originally created a Country field with the following values:

US
Canada

After a change in requirements, the new values for the field were:

Canada
Germany
Great Britain
Ireland
United States

After updating the site column, I then needed to update the hundreds of items in the list to use “United States” instead of “US”. Instead of updating hundreds of items manually, I decided to write a small web services console app. (I was also not able to update it in datasheet… due to content approval maybe???)

However, I quickly ran into problems when attempting to update the multi-select choice field.

The Setup:

My site column was defined with each choice for Country in alphabetical order:

Symptoms:

The symptoms of my problem were very strange. After running my app successfully, it seemed as if my updates were simply ignored by the server.

The item is successfully updated using the Lists.asmx (it even creates a new version!)
The item does not show the updated value for your multi-select choice field in the UI.

The Code:

Here is the very simple code that is creating the update message:

private static void AddCountryUpdate(ref StringBuilder sb, int count, string id, string newCountry)
{
    sb.AppendFormat("", count);
    sb.AppendFormat("{0}", id);
    sb.AppendFormat("{0}", newCountry);
    sb.Append("");
}

Calling the following code to update:

XmlDocument xmlDoc = new System.Xml.XmlDocument();
System.Xml.XmlElement elBatch = xmlDoc.CreateElement("Batch");
elBatch.InnerXml = sb.ToString();
XmlNode ndReturn = list.ListWebSvc.UpdateListItems(listName, elBatch);

The Results:

Attempting to update Country to be “;#United States;#Canada;#” resulted in a ”success” response (error code of 0×00000000) even when the update was NOT successful:

  ID="373,Update">
  >0x00000000>
   ows_ID="1311" ows_Country=";#United States;#Canada;#" ows_Modified="2009-10-29 16:01:05" ows__UIVersionString="6.0" />
>

Viewing this in the UI still shows the old value:

However, only after the values are in order, “;#Canada;#United States;#”, will the update actually happen.

 ID="223,Update">
  >0x00000000>
   ows_ID="1311" ows_Country=";#Canada;#United States;#" ows_Modified="2009-10-30 08:51:45" ows__UIVersionString="7.0" />
>

Viewing this in the UI shows the updated value:

Notice it still created a version 6.0 and 7.0:

Conclusion:

When updating a multi-select choice field using SharePoint’s Lists.asmx web service, the order of the choices in the update message are important. If they are out of order, it will not update.

SharePoint’s SPGridView, filtering, and apostrophes

Kit — Sat, 05 Sep 2009 06:10:43 +0000

The SPGridView is one of the most useful SharePoint controls. You can use it to do sorting, grouping, and filtering just like the out of the box List View Web Part does for regular lists and libraries. This makes it relatively easy to create a custom grid with your own data. Unfortunately, filtering with the SPGridView is a little quirky, especially if your data could potentially contain apostrophes.

Essentially, all you need to do is set a few quick properties to enable filtering on the SPGridView. (see the great tutorial on Reverse Alchemy for more information)

// Filtering
grid.AllowFiltering = true;
grid.FilterDataFields = ",Name,Region,Total Sales";
grid.FilteredDataSourcePropertyName = "FilterExpression";
grid.FilteredDataSourcePropertyFormat = "{1} = '{0}'";

However, what happens if you have an apostrophe for the value in one of your filters (for example filtering on the name of O’Reilly). Eventually, you will end up with a filter of:

Name = 'O'Reilly'

If this is the case, when you attempt to filter using that value you will get the error:

Syntax error: Missing operand after 'Reilly' operator

(See the question asked by Moo on StackOverflow)

So how do you prevent the apostrophes from messing up your filter?

protected override void OnPreRender(EventArgs e)
 {
     if (!string.IsNullOrEmpty(_gridDS.FilterExpression))
     {
         _gridDS.FilterExpression = string.Format(
             _grid.FilteredDataSourcePropertyFormat,
             _grid.FilterFieldValue.Replace("'", "''"),
             _grid.FilterFieldName);
     }
     base.OnPreRender(e);
 }

Where _gridDS is an ObjectDataSource (you must use an ObjectDataSource as opposed to setting the DataSource SPGridView property) and _grid is your SPGridView.

The solution is relatively simple… but what is happening behind the scenes? Actually, pretty much the same thing but without the replace. The SPGridView looks up your ObjectDataSource using the DataSourceID property. Once it has your ObjectDataSource, it then sets the property specified in FilteredDataSourcePropertyName (FilterExpression) to be the filter. Once you understand that behind the scenes, all it really is doing is setting the FilterExpression on your datasource, it is pretty easy to override the incorrect filter with a correct one.

Filtering a list by Workflow Status

Kit — Tue, 25 Aug 2009 18:25:59 +0000

The most recent problem I ran into was when I tried to filter out items that had a certain Workflow status in the list. More specifically, I was trying to filter on items that had errored out and had a status of “Error Occurred” in the list.

My first thought was to try to filter based on the text. Using a contains didn’t work; I got a message about you can only use a contains on Single line of text, Multiple line of text, or Choice fields.

The solution is to filter based on the integer value:

Listed below are the other values in the enum that you can use for the various states.

public enum SPWorkflowStatus
{
    NotStarted = 0,
    FailedOnStart = 1,
    InProgress = 2,
    ErrorOccurred = 3,
    StoppedByUser = 4,
    Completed = 5,
    FailedOnStartRetrying = 6,
    ErrorOccurredRetrying = 7,
    ViewQueryOverflow = 8,
    Max = 15,
}

Creating a SharePoint Alert with different EventTypes

Kit — Wed, 19 Aug 2009 01:55:00 +0000

I recently ran into a problem creating alerts in a web part for the current user. After the alert was added, no matter what I set the SPAlert’s EventType to, it always defaulted to All. I finally figured out a way around this problem thanks to a helpful post by erwin at sharepointology.

The workaround involves setting the eventtypeindex in the SPAlert Properties. Since I designed my web part to be configurable, an admin is able to specify the following web part properties

SPEventType WPPAlertEventType
(Add, All, Delete, Discussion, Modify)
SPAlertFrequency WPPAlertFrequency
(Daily, Immediate, Weekly)
int WPPAlertTimeHour
(the hour of the day 0 – 23, only applies to Daily and Weekly alerts)
int WPPAlertTimeDayOfWeek
(the day of the week 0 – 6, only applies to Weekly alerts)
bool WPPSendConfirmationEmail
(whether or not to send the email saying that they were signed up for the alert)

Unfortunately, you can’t just convert WPPAlertEventType and put it in “eventtypeindex” because SPEventType’s enums were defined to have wacky binary values.

// Create an Alert for this List
SPAlert alert = currentUser.Alerts.Add();
alert.AlertType = SPAlertType.List;
alert.AlertTemplate = list.AlertTemplate;
alert.AlwaysNotify = false;
 
// DOESN'T WORK SETTING THE EVENT TYPE
//alert.EventType = (SPEventType)WPPAlertEventType;
 
// you must set the eventtypeindex property
switch (WPPAlertEventType)
{
     case SPEventType.All:
          alert.Properties["eventtypeindex"] = "0";
          break;
     case SPEventType.Add:
          alert.Properties["eventtypeindex"] = "1";
          break;
     case SPEventType.Modify:
          alert.Properties["eventtypeindex"] = "2";
          break;
     case SPEventType.Delete:
          alert.Properties["eventtypeindex"] = "3";
          break;
     case SPEventType.Discussion:
          alert.Properties["eventtypeindex"] = "4";
          break;
     default:
          break;
}
 
alert.AlertFrequency = WPPAlertFrequency;
 
// get the config for daily/weekly alerts
 
// the hours can be anything from 0 to 23
bool alertTimeHourIsValid = (WPPAlertTimeHour >= 0 && WPPAlertTimeHour <= 23);
int alertTimeHour = alertTimeHourIsValid ? WPPAlertTimeHour : DEFAULT_WPPAlertTimeHour;
 
// the day of the week can be anything 0 to 6 (Sunday = 0 - Saturday = 6)
bool alertTimeDayOfWeekIsValid = (WPPAlertTimeDayOfWeek >= 0 && WPPAlertTimeDayOfWeek <= 6);
int alertTimeDayOfWeek = alertTimeDayOfWeekIsValid ? WPPAlertTimeDayOfWeek : DEFAULT_WPPAlertTimeDayOfWeek;
 
switch (WPPAlertFrequency)
{
     case SPAlertFrequency.Daily:
          DateTime dailyAlertTime = new DateTime(DateTime.Today.Year, DateTime.Today.Month, DateTime.Today.Day, alertTimeHour, 0, 0);
          alert.AlertTime = dailyAlertTime;
          break;
     case SPAlertFrequency.Immediate:
          break;
     case SPAlertFrequency.Weekly:
          DateTime weeklyAlertTime = new DateTime(DateTime.Today.Year, DateTime.Today.Month, DateTime.Today.Day, alertTimeHour, 0, 0); ;
          weeklyAlertTime = weeklyAlertTime.AddDays(alertTimeDayOfWeek - (double)weeklyAlertTime.DayOfWeek);
          alert.AlertTime = weeklyAlertTime;
          break;
     default:
          break;
}
alert.List = list;
alert.Title = string.Format("{0} ({1} {2})", list.Title, WPPAlertEventType, WPPAlertFrequency);
bool sendConfirmationEmail = WPPSendConfirmationEmail;
alert.Update(sendConfirmationEmail);

References:

How To Create Alerts Programmatically

AutoIt3 script to auto resize windows

Kit — Fri, 31 Jul 2009 14:58:09 +0000

One thing that bugs me all the time is when a window doesn’t remember the position that it was resized or moved to. Although it is more of a nuisance than anything else, I decided to write a little AutoIt3 script to automatically resize my Remote Desktop windows to be the certain place and size that I prefer them to be in.

The following script will find any windows that have “Remote Desktop” in the title and resize them to be their maximum height and width. In fact, I tweaked it a little bit so that the window actually falls outside of the screen. This way I have more screen real estate for the desktop that I’m working in and I will also be able to quickly move between windows on my desktop.

;********************************************************************************
; Filename: maximize_window.au3
; Author: Kit Menke
; Date: July 30, 2009
; Description:
;   Resizes any window matching a certain search string to the given dimensions.
;   Useful for Windows you find you have to constantly resize.
;********************************************************************************
 
; any window that contains the following string will be resized
$windowTitleContains = "Remote Desktop"
 
; only match exact title names in this script
Opt("WinTitleMatchMode", 3)     ;1=start, 2=subStr, 3=exact, 4=advanced, -1 to -4=Nocase
 
; the new dimensions of the window to be resized to
; top left corner (x,y) coordinates
$winX = -4
$winY = -29
; the window's new width and height
$winWidth = 1024 - $winX*2
$winHeight = 768 - $winY
 
; get the list of windows and the string you want to check for
$var = WinList()
 
For $i = 1 to $var[0][0]
  ; Only display visble windows that have a title matching our search string
  $windowTitle = $var[$i][0]
  $containsTitle = StringInStr($windowTitle,$windowTitleContains)
  If $windowTitle <> "" AND IsVisible($windowTitle) AND 0 <> $containsTitle Then
    ResizeWindowWithExactTitle($windowTitle)
  EndIf
Next
 
Exit
 
Func IsVisible($handle)
  If BitAnd( WinGetState($handle), 2 ) Then
    Return 1
  Else
    Return 0
  EndIf
EndFunc
 
Func ResizeWindowWithExactTitle($winTitle)
    If WinExists($winTitle) Then
        WinMove($winTitle, "", $winX, $winY, $winWidth, $winHeight)
    EndIf
EndFunc

I then set up a little CMD file to call my au3 file (assumes AutoIt3.exe is in the same directory as your script, but you can obviously make this be whatever you want):

AutoIt3.exe maximize_window.au3

And then I have a shortcut to that CMD file on my quicklaunch that I can call whenever I need to resize my windows.