COMPLETED LIST

1. Ryan - Get the FMFS application running on the FMSERVER machine

Installation default path - 64 vs. 32 bit

To support installation under the Miner and Miner\ArcFM Solution folder so that it works for both 32 and 64 bit machines, you need to create two registry searches in the Setup project. The first registry search to support 64 bit machines would look for H_KEY_LOCAL_MACHINE\SOFTWARE\Wow6432Node\Miner and Miner and get the value of the LastInstallDir.  A second registry search for 32 bit machines would look at the same location minus the Wow6432Node.  Importantly both searches should set the same property (MMPATH in the example below).  You then use that MMPATH variable as the value for the Application Folder's DefaultLocation property as shown below. When you run the installer, the correct registry search is magically performed and it seems to just work.

IMPORTANT NOTE: Visual Studio will soon no longer support Setup projects:

http://blogs.msdn.com/b/buckh/archive/2011/03/17/visual-studio-setup-projects-vdproj-will-not-ship-with-future-versions-of-vs.aspx

TASK LIST

1. Neil - Get attribute viewer working on FMFS application
2. Neil - On the splice viewer report for FMFS, the graphics aren't going away.  This needs to get fixed. 
3. Neil - The Trace tab should be removed from the FMFS viewer
4. Paul - Work on a new report for the SAM forecast

Creating labels inside of tables

Ryan had a requirement to get labels to position themselves inside of tables as shown in the screen shot below. This doesn't necessarily have to involve the use of AAL (although it is easier if you do use it), but rather the use of a custom true type font, label classes, and a familiarity with Maplex.
Here are the important facts about how these labels were created.

Click to enlarge (labels inside of tables)

• I created a custom true type font using some try and buy software.  The capital letter "A" is the only letter that I defined.  In this case, it is a 5 row x4 column grid with the top row spanning the four columns.  This becomes the background table that the labels sit in.
• I used AAL to create a simple label expression using the font above but importantly chose the option to use label classes. The label expression for this class is just the letter "A" and is in the default class. 
• I created a second label class (I just called in Layer2) with no SQL expression so that it always draws, and I created an AAL label expression for this too : "123-456 | ABCD | EFGH | IJKL | MNOP" where the | character is a line-break. Now in reality, the data could of course be derived using something more complex than a simple string (e.g. use the Relationship labeler).
• You need to tweak some properties in Maplex so that labels always appear and that they are drawn 50% of the way along the line.  Having them draw 50% provides guaranteed placement (a "best" placement might result in the labels from one class going to a different spot than the second class, and remember, they have to line up).  If you are labeling points, this is easier...just choose a positioning strategy in Maplex that provides guaranteed placement. 
• You will likely need to tweak the label symbol for the data within the cells (e.g.  "123-456 | ABCD | EFGH | IJKL | MNOP").  I used a courier new font so that I had consistent spacing.  I also had to specify an X and Y offset, modify the character spacing and modify the "leading" which is essentially the line-spacing. Remember also to set the label offset for this class to 50% of the way along the line. 
• It is important to have / respect a reference scale for this layer.  That way the labels will scale appropriately when you zoom in and out. 
• Last thing that I can think of now is an important setting on the Conflict Resolution tab.  Make sure to choose the option to "Never Remove Labels (overlap)".  In this scenario, we actually want our labels from different classes to overlap.

Because the table is a character in a font,
you can easily set its color!

Public ftp site

User name = public
password = Sn00py!!   (those are zero's not letters)

Debugging components in ArcMap - Start External program

The trick to debugging components in ArcMap is to set the Startup program on the Debug tab in Visual studio as shown:

Set the path to:

C:\Program Files (x86)\ArcGIS\Desktop10.0\Bin\ArcMap.exe

Telvent.SE.SWGasQARules - QA rule to check for Excess Flow Valve

The Telvent.SE.SWGasQARules contains a QA rule that checks for the necessity of an Excess Flow Valve (EFV).  It was desgined to work on SW Gas data with minimal configuration (the EXCESSFLOWVALVE model name needs to be added and the QA rule assigned to Service).  The idea with the QA rule was to check if an EFV valve is required using the following logic:

1 - If the Service being QA'ed does not branch (meaning that there is not a three way intersection with all three lines being service) then you must have an Excess Flow Valve present.  In this case, a QA error is generated.  In this, the most simple negative case, you typically just see a single service line feeding a house without a EFV
2- A single service line with an EFV is OK
3 - A branched service line without an EFV is OK
4 - A branched service line with an EFV results in a QA Error (which is described as a warning in the QA/QC tab).

CONFIGURATION -

• RegX the .dll
• Add model name EXCESSFLOWVALVE
• Verify that SERVICEPOINT uniquely identifies MeterSetting (e.g. Riser) as the only feature class.  Note that this may cause problems with Minerville data or other geodatabases where there is an electric dataset which has a ServicePoint feature class. 
• Verify that the SERVICE model name exists on the Service feature class. 
• Add the QA rule to the Service Line - It is name Telvent.SE.SWGasQA or something like that...it might have the word EFV in it too.