<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.0 Transitional//EN">
<HTML xmlns="http://www.w3.org/TR/REC-html40" xmlns:v =
"urn:schemas-microsoft-com:vml" xmlns:o =
"urn:schemas-microsoft-com:office:office" xmlns:w =
"urn:schemas-microsoft-com:office:word" xmlns:m =
"http://schemas.microsoft.com/office/2004/12/omml"><HEAD>
<META http-equiv=Content-Type content="text/html; charset=us-ascii">
<META content="MSHTML 6.00.6000.17080" name=GENERATOR>
<STYLE>@font-face {
font-family: Calibri;
}
@font-face {
font-family: Tahoma;
}
@page WordSection1 {size: 8.5in 11.0in; margin: 1.0in 1.0in 1.0in 1.0in; }
P.MsoNormal {
FONT-SIZE: 12pt; MARGIN-LEFT: 0in; MARGIN-RIGHT: 0in; FONT-FAMILY: "Times New Roman","serif"; mso-margin-top-alt: auto; mso-margin-bottom-alt: auto; mso-believe-normal-left: yes
}
LI.MsoNormal {
FONT-SIZE: 12pt; MARGIN-LEFT: 0in; MARGIN-RIGHT: 0in; FONT-FAMILY: "Times New Roman","serif"; mso-margin-top-alt: auto; mso-margin-bottom-alt: auto; mso-believe-normal-left: yes
}
DIV.MsoNormal {
FONT-SIZE: 12pt; MARGIN-LEFT: 0in; MARGIN-RIGHT: 0in; FONT-FAMILY: "Times New Roman","serif"; mso-margin-top-alt: auto; mso-margin-bottom-alt: auto; mso-believe-normal-left: yes
}
A:link {
COLOR: blue; TEXT-DECORATION: underline; mso-style-priority: 99
}
SPAN.MsoHyperlink {
COLOR: blue; TEXT-DECORATION: underline; mso-style-priority: 99
}
A:visited {
COLOR: purple; TEXT-DECORATION: underline; mso-style-priority: 99
}
SPAN.MsoHyperlinkFollowed {
COLOR: purple; TEXT-DECORATION: underline; mso-style-priority: 99
}
SPAN.EmailStyle17 {
COLOR: #1f497d; FONT-FAMILY: "Calibri","sans-serif"; mso-style-type: personal-reply
}
.MsoChpDefault {
FONT-SIZE: 10pt; mso-style-type: export-only
}
DIV.WordSection1 {
page: WordSection1
}
</STYLE>
<![if mso 9]><style>p.MsoNormal
{margin-left:3.0pt;}
</style><![endif]><!--[if gte mso 9]><xml>
<o:shapedefaults v:ext="edit" spidmax="1026" />
</xml><![endif]--><!--[if gte mso 9]><xml>
<o:shapelayout v:ext="edit">
<o:idmap v:ext="edit" data="1" />
</o:shapelayout></xml><![endif]--></HEAD>
<BODY lang=EN-US style="MARGIN: 3pt 3pt 0.75pt" vLink=purple link=blue>
<DIV dir=ltr align=left><SPAN class=354503716-21122010><FONT face=Arial
color=#0000ff size=2>Shad,</FONT></SPAN></DIV>
<DIV dir=ltr align=left><SPAN class=354503716-21122010><FONT face=Arial
color=#0000ff size=2>Will the new tool have all the functionality of the VBA
tool? I'm thinking of printing from a list or printing from a range.
</FONT></SPAN></DIV>
<DIV dir=ltr align=left><SPAN class=354503716-21122010><FONT face=Arial
color=#0000ff size=2></FONT></SPAN> </DIV>
<DIV dir=ltr align=left><SPAN class=354503716-21122010><FONT face=Arial
color=#0000ff size=2>also I have a couple of inconveniences with 10 service
pack 1 that I'd like to post somewhere for us to consider, as work around
tools or bug fix campaigns directed at ESRI. They are both things
that were not a problem in 9.3 and require extra steps in
10:</FONT></SPAN></DIV>
<DIV dir=ltr align=left><SPAN class=354503716-21122010><FONT face=Arial
color=#0000ff size=2></FONT></SPAN> </DIV>
<DIV dir=ltr align=left><SPAN class=354503716-21122010><FONT face=Arial
color=#0000ff size=2>1. Inability to use Attribute tool on editable table with
join to read-only table.</FONT></SPAN></DIV>
<DIV dir=ltr align=left><SPAN class=354503716-21122010><FONT face=Arial
color=#0000ff size=2></FONT></SPAN> </DIV>
<DIV><SPAN class=354503716-21122010></SPAN><FONT face=Arial><FONT
color=#0000ff><FONT
size=2>2. Inability to set edit target <SPAN
class=354503716-21122010>for</SPAN> <SPAN class=354503716-21122010>feature
linked </SPAN>annotation <SPAN class=354503716-21122010>"</SPAN><SPAN
class=354503716-21122010>cntrl + w</SPAN>" <SPAN
class=354503716-21122010>get source
</SPAN>shortcut without entering preliminary dummy text.</FONT></FONT></FONT></DIV>
<DIV><FONT face=Arial><FONT color=#0000ff><FONT
size=2></FONT></FONT></FONT> </DIV>
<DIV><SPAN class=354503716-21122010></SPAN><FONT face=Arial><FONT
color=#0000ff><FONT size=2>D<SPAN class=354503716-21122010>a</SPAN><SPAN
class=354503716-21122010>vid</SPAN></FONT></FONT></FONT><BR></DIV>
<DIV class=OutlookMessageHeader lang=en-us dir=ltr align=left>
<HR tabIndex=-1>
<FONT face=Tahoma size=2><B>From:</B>
ormap-tech-bounces@listsmart.osl.state.or.us
[mailto:ormap-tech-bounces@listsmart.osl.state.or.us] <B>On Behalf Of </B>Shad
Campbell<BR><B>Sent:</B> Monday, December 20, 2010 6:13 PM<BR><B>To:</B> DEAN
ANDERSON; ORMAP Tech List<BR><B>Subject:</B> Re: [ORMAP-Tech] ORMAP Tools
Meeting Notes<BR></FONT><BR></DIV>
<DIV></DIV>
<DIV class=WordSection1>
<P class=MsoNormal><SPAN
style="FONT-SIZE: 11pt; COLOR: #1f497d; FONT-FAMILY: 'Calibri','sans-serif'">Dean
and other Tool Committee members,<o:p></o:p></SPAN></P>
<P class=MsoNormal><SPAN
style="FONT-SIZE: 11pt; COLOR: #1f497d; FONT-FAMILY: 'Calibri','sans-serif'">A
quick update. I have attached the Project Specifications (including hours)
for updating the Map Production code to ArcPy. Please provide
any feedback you may have. I also moved the Visual Studio 2010 solution
files to the trunk and branched the final Visual Studio 2008 files on
SourceForge. Lastly, neither David or I have been able to reproduce
the bug that Jon was experiencing. At this point I’m thinking it’s
something specific to Jon’s PC but he is setting up another test environment and
will let us know what he finds. There is not much I can do at this
point.<o:p></o:p></SPAN></P>
<P class=MsoNormal><SPAN
style="FONT-SIZE: 11pt; COLOR: #1f497d; FONT-FAMILY: 'Calibri','sans-serif'">Let
me know when I have the green light to start work on the Map Production/ArcPy
stuff.<o:p></o:p></SPAN></P>
<P class=MsoNormal><SPAN
style="FONT-SIZE: 11pt; COLOR: #1f497d; FONT-FAMILY: 'Calibri','sans-serif'">-Shad<o:p></o:p></SPAN></P>
<P class=MsoNormal><SPAN
style="FONT-SIZE: 11pt; COLOR: #1f497d; FONT-FAMILY: 'Calibri','sans-serif'"><o:p> </o:p></SPAN></P>
<P class=MsoNormal><SPAN
style="FONT-SIZE: 11pt; COLOR: #1f497d; FONT-FAMILY: 'Calibri','sans-serif'"><o:p> </o:p></SPAN></P>
<DIV>
<DIV
style="BORDER-RIGHT: medium none; PADDING-RIGHT: 0in; BORDER-TOP: #b5c4df 1pt solid; PADDING-LEFT: 0in; PADDING-BOTTOM: 0in; BORDER-LEFT: medium none; PADDING-TOP: 3pt; BORDER-BOTTOM: medium none">
<P class=MsoNormal style="MARGIN: 0in 0in 0pt"><B><SPAN
style="FONT-SIZE: 10pt; FONT-FAMILY: 'Tahoma','sans-serif'">From:</SPAN></B><SPAN
style="FONT-SIZE: 10pt; FONT-FAMILY: 'Tahoma','sans-serif'">
ormap-tech-bounces@listsmart.osl.state.or.us
[mailto:ormap-tech-bounces@listsmart.osl.state.or.us] <B>On Behalf Of </B>DEAN
ANDERSON<BR><B>Sent:</B> Friday, December 17, 2010 1:07 PM<BR><B>To:</B> ORMAP
Tech List<BR><B>Subject:</B> [ORMAP-Tech] ORMAP Tools Meeting
Notes<o:p></o:p></SPAN></P></DIV></DIV>
<P class=MsoNormal><o:p> </o:p></P>
<DIV>
<P class=MsoNormal style="MARGIN: 0in 0in 0pt"><SPAN
style="FONT-SIZE: 10pt; FONT-FAMILY: 'Tahoma','sans-serif'">ORMAP ARCMAP
December Tools Programmer Committee <BR>Notes from Dean Anderson - Tools
Coordinator <BR><BR>1. Review Testing Results<o:p></o:p></SPAN></P></DIV>
<DIV>
<P class=MsoNormal style="MARGIN: 0in 0in 0pt"><SPAN
style="FONT-SIZE: 10pt; FONT-FAMILY: 'Tahoma','sans-serif'"> <o:p></o:p></SPAN></P></DIV>
<DIV>
<P class=MsoNormal style="MARGIN: 0in 0in 0pt"><SPAN
style="FONT-SIZE: 10pt; FONT-FAMILY: 'Tahoma','sans-serif'">Everything looks
pretty good for going to ArcMap 10. Shad is about done. John found a
bug that Shad thinks he should get cleared up pretty quick. Shad is going to get
bill to Phil. We approve him paying it and closing the conversion to ArcMap10
project. <BR><BR>2. Moving ArcMap 10 to trunk <o:p></o:p></SPAN></P></DIV>
<DIV>
<P class=MsoNormal style="MARGIN: 0in 0in 0pt"><SPAN
style="FONT-SIZE: 10pt; FONT-FAMILY: 'Tahoma','sans-serif'"> <o:p></o:p></SPAN></P></DIV>
<DIV>
<P class=MsoNormal style="MARGIN: 0in 0in 0pt"><SPAN
style="FONT-SIZE: 10pt; FONT-FAMILY: 'Tahoma','sans-serif'">We are going to
replace the download with ArcMap 10. Shad is going to..<BR>- Save 9.3 to
branch<BR>- Delete 9.3 in trunk <BR>- Update Trunk with 10 <BR><BR>This should
be done by January 1. Dean will get it set to download (with David's
help.) David will work with Dean on getting permissions and
training on source forge to do this. <BR><BR>Once this is done Robert is
going to copy trunk to branch and make the updates for annotation. We will then
move this to trunk at some future time. <o:p></o:p></SPAN></P></DIV>
<DIV>
<P class=MsoNormal style="MARGIN: 0in 0in 0pt"><SPAN
style="FONT-SIZE: 10pt; FONT-FAMILY: 'Tahoma','sans-serif'"> <o:p></o:p></SPAN></P></DIV>
<DIV>
<P class=MsoNormal style="MARGIN: 0in 0in 0pt"><SPAN
style="FONT-SIZE: 10pt; FONT-FAMILY: 'Tahoma','sans-serif'">3. Going to ArcMap
10 <o:p></o:p></SPAN></P></DIV>
<DIV>
<P class=MsoNormal style="MARGIN: 0in 0in 0pt"><SPAN
style="FONT-SIZE: 10pt; FONT-FAMILY: 'Tahoma','sans-serif'"> <o:p></o:p></SPAN></P></DIV>
<DIV>
<P class=MsoNormal style="MARGIN: 0in 0in 0pt"><SPAN
style="FONT-SIZE: 10pt; FONT-FAMILY: 'Tahoma','sans-serif'">Programmers found a
couple little things counties will have to do when going to 10. Lane,
Deschutes, Polk and Clackamas are all in testing mode. It appears that you
can run the tests on the production database. Lane and Deschutes have set this
up. The big issue when going to ArcMap 10 is to be sure to uninstall the
tools prior unstalling 9.3. If you do not the tool install will not
work. We will put notes on the upgrade process on the web
site.<BR><BR>4 Annotation Demo <o:p></o:p></SPAN></P></DIV>
<DIV>
<P class=MsoNormal style="MARGIN: 0in 0in 0pt"><SPAN
style="FONT-SIZE: 10pt; FONT-FAMILY: 'Tahoma','sans-serif'"> <o:p></o:p></SPAN></P></DIV>
<DIV>
<P class=MsoNormal style="MARGIN: 0in 0in 0pt"><SPAN
style="FONT-SIZE: 10pt; FONT-FAMILY: 'Tahoma','sans-serif'">Robert showed
this. Demo worked well and will be moved to trunk. Talked about
making it work without annotation distance/direction pairs. We will do this
at some future time as an update. <BR><BR>5.
Training<o:p></o:p></SPAN></P></DIV>
<DIV>
<P class=MsoNormal style="MARGIN: 0in 0in 0pt"><SPAN
style="FONT-SIZE: 10pt; FONT-FAMILY: 'Tahoma','sans-serif'"> <o:p></o:p></SPAN></P></DIV>
<DIV>
<P class=MsoNormal style="MARGIN: 0in 0in 0pt"><SPAN
style="FONT-SIZE: 10pt; FONT-FAMILY: 'Tahoma','sans-serif'">Deschutes, Polk, and
Lane agreed to do work on training. The goal is to move training materials to a
WIKI so that counties have the materials available to them to do training when
they needed it. We discussed a number of different training alternatives
and thought this would work best. <BR><BR>6. Wiki <o:p></o:p></SPAN></P></DIV>
<DIV>
<P class=MsoNormal style="MARGIN: 0in 0in 0pt"><SPAN
style="FONT-SIZE: 10pt; FONT-FAMILY: 'Tahoma','sans-serif'"> <o:p></o:p></SPAN></P></DIV>
<DIV>
<P class=MsoNormal style="MARGIN: 0in 0in 0pt"><SPAN
style="FONT-SIZE: 10pt; FONT-FAMILY: 'Tahoma','sans-serif'">Dean will setup a
wiki by January 10th. He will send out an outline of WKI topics
soon. <BR><BR>7. Developer Programmer Comments: <o:p></o:p></SPAN></P></DIV>
<DIV>
<P class=MsoNormal style="MARGIN: 0in 0in 0pt"><SPAN
style="FONT-SIZE: 10pt; FONT-FAMILY: 'Tahoma','sans-serif'"> <o:p></o:p></SPAN></P></DIV>
<DIV>
<P class=MsoNormal style="MARGIN: 0in 0in 0pt"><SPAN
style="FONT-SIZE: 10pt; FONT-FAMILY: 'Tahoma','sans-serif'">Was noted that it is
important to have Automatic update turned on. Need to check feature class to
sure function turn one. This type of validation is important so that apps do not
blow up. This topic will be addressed in more detail on the WIKI<BR><BR>8.
Map Production - Map production folks met. Shad should have a proposal for
review in a week or so. <o:p></o:p></SPAN></P></DIV>
<DIV>
<P class=MsoNormal style="MARGIN: 0in 0in 0pt"><SPAN
style="FONT-SIZE: 10pt; FONT-FAMILY: 'Tahoma','sans-serif'"> <o:p></o:p></SPAN></P></DIV>
<DIV>
<P class=MsoNormal style="MARGIN: 0in 0in 0pt"><SPAN
style="FONT-SIZE: 10pt; FONT-FAMILY: 'Tahoma','sans-serif'"> <o:p></o:p></SPAN></P></DIV></DIV></BODY></HTML>