<?xml version="1.0" encoding="UTF-8" ?>
<?xml-stylesheet type="text/xsl" href="https://communities.bentley.com/cfs-file/__key/system/syndication/rss.xsl" media="screen"?><rss version="2.0" xmlns:dc="http://purl.org/dc/elements/1.1/" xmlns:slash="http://purl.org/rss/1.0/modules/slash/" xmlns:wfw="http://wellformedweb.org/CommentAPI/"><channel><title>MX VB6 / SDK normal issue</title><link>https://communities.bentley.com/products/road___site_design/f/geopak-inroads-mx-openroads-forum/45502/mx-vb6-sdk-normal-issue</link><description>Hi,
 
 
 I&amp;#39;m currently developing a program with VB6 using the MX SDK. Thr program is required to perform a lot of normal calculations from points onto a master string.
 
 
I am using the &amp;#39;MFWPSMcNormal&amp;#39; method from the MFWSystemBuild object to</description><dc:language>en-US</dc:language><generator>Telligent Community 12</generator><item><title>Re: MX VB6 / SDK normal issue</title><link>https://communities.bentley.com/thread/102638?ContentTypeID=1</link><pubDate>Tue, 22 Dec 2009 02:28:08 GMT</pubDate><guid isPermaLink="false">6dad98f5-dbc9-4c4d-a9ba-e9da8dc6aa8e:65d94a6c-4b6f-447d-8951-5cc66c9618f2</guid><dc:creator>A Milford</dc:creator><description>&lt;p&gt;
Thanks Phil, thats very handy
&lt;/p&gt;
&lt;p&gt;
I have also rewritten the normal code to use the MX 996 options, but used the MFWGetData option to read from the temporary data file. The good thing is that it works on other computers, downside is that it takes a lot longer to process. I'll try to plug your code in and see if I can get a quicker result.
&lt;/p&gt;
&lt;p&gt;
Thanks
&lt;/p&gt;
&lt;p&gt;
AM
&lt;/p&gt;
&lt;p&gt;
&amp;nbsp;
&lt;/p&gt;&lt;div style="clear:both;"&gt;&lt;/div&gt;</description><enclosure url="https://communities.bentley.com/cfs-file/__key/telligent-evolution-components-attachments/00-5922-01-00-00-10-26-38/996GetGataExample.txt" length="4011" type="text/plain" /></item><item><title>Re: MX VB6 / SDK normal issue</title><link>https://communities.bentley.com/thread/102389?ContentTypeID=1</link><pubDate>Sat, 19 Dec 2009 03:47:54 GMT</pubDate><guid isPermaLink="false">6dad98f5-dbc9-4c4d-a9ba-e9da8dc6aa8e:3645bfd5-3568-4b4e-bea9-dd15650cd18a</guid><dc:creator>Philip Davies</dc:creator><description>&lt;p&gt;
Andrew,
&lt;/p&gt;
&lt;p&gt;
I had trouble with this routine when building the RTA's CTC Report. In situations where more than one normal is possible only the first is returned and no indication is given that other normals exist. I end up using a 996 report and trolling through the output the get the correct result. The code from my project is attached for your reference.
&lt;/p&gt;
&lt;p&gt;
&amp;nbsp;I would suggest looking at the curve fitting values as this is usually the cause of most heartache with normals.
&lt;/p&gt;
&lt;p&gt;
Regards&lt;br /&gt;
Phil
&lt;/p&gt;&lt;div style="clear:both;"&gt;&lt;/div&gt;</description><enclosure url="https://communities.bentley.com/cfs-file/__key/telligent-evolution-components-attachments/00-5922-01-00-00-10-23-89/996codeexample.txt" length="8359" type="text/plain" /></item></channel></rss>