<?xml version="1.0" encoding="UTF-8"?>
<rss version="2.0"
	xmlns:content="http://purl.org/rss/1.0/modules/content/"
	xmlns:wfw="http://wellformedweb.org/CommentAPI/"
	xmlns:dc="http://purl.org/dc/elements/1.1/"
	xmlns:atom="http://www.w3.org/2005/Atom"
	xmlns:sy="http://purl.org/rss/1.0/modules/syndication/"
	xmlns:slash="http://purl.org/rss/1.0/modules/slash/"
	>

<channel>
	<title>Solar Polar &#187; OpenEdge</title>
	<atom:link href="http://solarpolar.co.uk/category/openedge/feed/" rel="self" type="application/rss+xml" />
	<link>http://solarpolar.co.uk</link>
	<description>Dave Walker, Malton, North Yorkshire. Blog, Music, Web and OpenEdge</description>
	<lastBuildDate>Wed, 16 May 2012 20:32:33 +0000</lastBuildDate>
	<language>en</language>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
	<generator>http://wordpress.org/?v=3.3.2</generator>
		<item>
		<title>Setting up Webspeed with IIS 7.5 Windows 7</title>
		<link>http://solarpolar.co.uk/openedge-webspeed-with-iis-7-5-windows-7/</link>
		<comments>http://solarpolar.co.uk/openedge-webspeed-with-iis-7-5-windows-7/#comments</comments>
		<pubDate>Wed, 20 Apr 2011 20:05:29 +0000</pubDate>
		<dc:creator>admin21</dc:creator>
				<category><![CDATA[OpenEdge]]></category>

		<guid isPermaLink="false">http://www.solarpolar.co.uk/?p=608</guid>
		<description><![CDATA[<p>The following instructions can be used to create a basic setup for OpenEdge (10.2b) Webspeed development.</p>
<p>The information has been gleaned from the following source &#8211; Progress Knowledgebase, ProgressTalk.com, The OpenEdge Hive and also the manuals!  Thanks to all who put info online, especially Scott Auge who has posted some very informative videos.

Setting up IIS 7.5 under Windows 7</p>
<p>1) First ensure that Apache Server isn&#8217;t running already on your machine.  I usually have one running and both servers on my machine use port 80, so only one can be used at once  (there may be a way to get both running, but in practice this wouldn&#8217;t happen).</p>
<p>2) Next we check that IIS and the sub components for CGI and ISAPI are actually installed.</p>
<p>- Start by double checking if CGI/ISAPI features of IIS are installed going to:
Control Panel -&#62; Program and Features -&#62; ...]]></description>
			<content:encoded><![CDATA[<p>The following instructions can be used to create a basic setup for OpenEdge (10.2b) Webspeed development.</p>
<p>The information has been gleaned from the following source &#8211; Progress Knowledgebase, ProgressTalk.com, The OpenEdge Hive and also the manuals!  Thanks to all who put info online, especially Scott Auge who has posted some very informative videos.<br />
<span id="more-608"></span><br />
Setting up IIS 7.5 under Windows 7</p>
<p>1) First ensure that Apache Server isn&#8217;t running already on your machine.  I usually have one running and both servers on my machine use port 80, so only one can be used at once  (there may be a way to get both running, but in practice this wouldn&#8217;t happen).</p>
<p>2) Next we check that IIS and the sub components for CGI and ISAPI are actually installed.</p>
<p>- Start by double checking if CGI/ISAPI features of IIS are installed going to:<br />
Control Panel -&gt; Program and Features -&gt; Turn Windows features on or off -&gt; will open Windows Features window -&gt; (Internet Information Services)</p>
<p>- World Wide Web Services Application Development Features -&gt; confirm that CGI, ISAPI Extensions are listed as status installed/ticked.</p>
<p>3) The IIS service should be running.  Check in Services under World Wide Web Publishing Service.</p>
<p>4) Now Run IIS from Administrative Tools.</p>
<p>Create a virtual directory &#8220;scripts&#8221; (you name it).</p>
<p>IIS Manager -&gt; Web Sites -&gt; Default Web Site -&gt; Add Virtual Directory -&gt; Alias: scripts, Physical path: c:inetpubscripts (or where cgiip.exe and/or wsisa.dll are located)</p>
<p>3) Allow cgiip.exe / wsisa.dll to run on IIS:</p>
<p>Go to IIS Manager -&gt; Sites -&gt; Default Web Site -&gt; scripts</p>
<p>In &#8220;Features View&#8221; choose the option &#8220;Handler Mappings&#8221;</p>
<p>In the &#8220;Actions&#8221; pane, click on &#8220;Add Module Mapping&#8221;</p>
<p>Enter &#8220;*.wsc&#8221; in the &#8220;Request path&#8221; field</p>
<p>In the &#8220;Module&#8221; list choose &#8221; CgiModule&#8221;</p>
<p>In the &#8220;Executable&#8221; filed enter the path to your cgiip.exe, e.g.:<br />
[install-dir]/bin/cgiip.exe %s %s<br />
If [install-dir] contains spaces then it will have to be enclosed with double quotes.</p>
<p>There will be a question if you want to add the extension with an &#8220;Allowed&#8221; entry to the ISAPI and CGI restrictions list. Answer &#8220;Yes&#8221;.</p>
<p>IIS Manager -&gt; Web Sites -&gt; Default Web Site -&gt; scripts -&gt; handler mappings -&gt; edit handler permissions -&gt; tick on &#8220;execute&#8221;.</p>
<p>4) Create a virtual folder for webspeed images and doc going to:<br />
IIS Manager -&gt; Web Sites -&gt; Default Web Site -&gt; Add Virtual Directory -&gt; Alias: webspeeed&lt;version&gt;, Physical path: &lt;Install Directory&gt;webspeed</p>
<p>&nbsp;</p>
<p>Step 1</p>
<p>Ensure that your OpenEdge AdminService is running</p>
<p>Run Progress Explorer</p>
<p>As we&#8217;re running a basic setup we&#8217;ll just simply startup the WebSpeed wsbroker1 and also the NameServer NS1 with default settings (we&#8217;ll not connect any databases yet)</p>
<div id="attachment_611" class="wp-caption alignnone" style="width: 310px"><a href="http://solarpolar.co.uk/wp-content/uploads/2011/03/progress-explorer.jpg" rel="lightbox[608]" title="Progress Explorer"><img class="size-medium wp-image-611" title="Progress Explorer" src="http://solarpolar.co.uk/wp-content/uploads/2011/03/progress-explorer-300x181.jpg" alt="" width="300" height="181" /></a><p class="wp-caption-text">Progress Explorer - Starting WebServer / NameServer</p></div>
<p>Now we need to ensure that IIS is installed.</p>
<p>&nbsp;</p>
]]></content:encoded>
			<wfw:commentRss>http://solarpolar.co.uk/openedge-webspeed-with-iis-7-5-windows-7/feed/</wfw:commentRss>
		<slash:comments>0</slash:comments>
		</item>
		<item>
		<title>View all registered OCX and DLLs</title>
		<link>http://solarpolar.co.uk/view-all-registered-ocx-and-dlls/</link>
		<comments>http://solarpolar.co.uk/view-all-registered-ocx-and-dlls/#comments</comments>
		<pubDate>Tue, 15 Mar 2011 12:55:30 +0000</pubDate>
		<dc:creator>admin21</dc:creator>
				<category><![CDATA[OpenEdge]]></category>
		<category><![CDATA[OpenPeople]]></category>
		<category><![CDATA[Web Stuff]]></category>

		<guid isPermaLink="false">http://www.solarpolar.co.uk/?p=605</guid>
		<description><![CDATA[<p>Now and again I have problems with registered .ocx and .dll files.</p>
<p>I found a program that will display and allow you to edit / register / unregister the files.</p>
<p>It&#8217;s called RegDllView and you can find it here. http://www.nirsoft.net/utils/registered_dll_view.html</p>
<p>Remember to run it as an Administrator if you&#8217;re using Windows 7.</p>
]]></description>
			<content:encoded><![CDATA[<p>Now and again I have problems with registered .ocx and .dll files.</p>
<p>I found a program that will display and allow you to edit / register / unregister the files.</p>
<p>It&#8217;s called RegDllView and you can find it here. <a title="RegDllView" href="http://www.nirsoft.net/utils/registered_dll_view.html">http://www.nirsoft.net/utils/registered_dll_view.html</a></p>
<p>Remember to run it as an Administrator if you&#8217;re using Windows 7.</p>
]]></content:encoded>
			<wfw:commentRss>http://solarpolar.co.uk/view-all-registered-ocx-and-dlls/feed/</wfw:commentRss>
		<slash:comments>1</slash:comments>
		</item>
		<item>
		<title>Progress / OpenEdge 10.x License Update</title>
		<link>http://solarpolar.co.uk/progress-openedge-10-x-license-update/</link>
		<comments>http://solarpolar.co.uk/progress-openedge-10-x-license-update/#comments</comments>
		<pubDate>Mon, 14 Feb 2011 11:52:58 +0000</pubDate>
		<dc:creator>admin21</dc:creator>
				<category><![CDATA[OpenEdge]]></category>

		<guid isPermaLink="false">http://www.solarpolar.co.uk/?p=595</guid>
		<description><![CDATA[<p>When attempting to update the license details the installer checks for already running instances of Progress&#8230; but finds itself and stops!</p>
<p>To stop this change the startup target on the Update Icon from:</p>
c:installationdirsetup.exe -u
<p>to</p>
c:installationdirsetup.exe u
]]></description>
			<content:encoded><![CDATA[<p>When attempting to update the license details the installer checks for already running instances of Progress&#8230; but finds itself and stops!</p>
<p>To stop this change the startup target on the Update Icon from:</p>
<pre>c:installationdirsetup.exe -u</pre>
<p>to</p>
<pre>c:installationdirsetup.exe u</pre>
]]></content:encoded>
			<wfw:commentRss>http://solarpolar.co.uk/progress-openedge-10-x-license-update/feed/</wfw:commentRss>
		<slash:comments>0</slash:comments>
		</item>
		<item>
		<title>Checking a Progress / OpenEdge Database for MSSQL conversion</title>
		<link>http://solarpolar.co.uk/checking-a-progress-openedge-database-for-mssql-conversion/</link>
		<comments>http://solarpolar.co.uk/checking-a-progress-openedge-database-for-mssql-conversion/#comments</comments>
		<pubDate>Wed, 17 Nov 2010 11:54:36 +0000</pubDate>
		<dc:creator>admin21</dc:creator>
				<category><![CDATA[OpenEdge]]></category>

		<guid isPermaLink="false">http://www.solarpolar.co.uk/?p=528</guid>
		<description><![CDATA[<p>When I&#8217;m converting an OpenEdge database to a MS SQL database there are a few issues to consider.</p>
<p>One important one is that natice OE databases allow users to &#8220;overfill&#8221; database fields e.g. if I have a field called employee.name defined as CHARACTER FORMAT &#8220;x(20)&#8221; but have a name which is 30 characters then that is no problem.</p>
<p>In MSSQL however, that will fail.</p>
<p>So when we convert our database Progress supply &#8220;dbtool&#8221; which trawls through the content of each field checking for overfilling.  It will report the fields then ask to change the internal SQL Width value which I then use when migrating the database.</p>
<p>Unfortunately this tool doesn&#8217;t handle database array fields so I&#8217;ve amended that procedure and posted it below for reference.</p>

/* Program to Verify / Change SQL Width Sizes within a Progress

database.

This program should be run BEFORE any Schema Migration ...]]></description>
			<content:encoded><![CDATA[<p>When I&#8217;m converting an OpenEdge database to a MS SQL database there are a few issues to consider.</p>
<p>One important one is that natice OE databases allow users to &#8220;overfill&#8221; database fields e.g. if I have a field called employee.name defined as CHARACTER FORMAT &#8220;x(20)&#8221; but have a name which is 30 characters then that is no problem.</p>
<p>In MSSQL however, that will fail.</p>
<p>So when we convert our database Progress supply &#8220;dbtool&#8221; which trawls through the content of each field checking for overfilling.  It will report the fields then ask to change the internal SQL Width value which I then use when migrating the database.</p>
<p>Unfortunately this tool doesn&#8217;t handle database array fields so I&#8217;ve amended that procedure and posted it below for reference.</p>
<pre>
/* Program to Verify / Change SQL Width Sizes within a Progress

database.

This program should be run BEFORE any Schema Migration Process

: Dave Walker - June 2010

:

: The Program will add 50% to the width if it's exceeded

*/

FORM

_file-name LABEL "Processing File"

_field-name

WITH FRAME xx SIDE-LABELS 1 COL WIDTH 78.

DEFINE TEMP-TABLE sqlw

FIELD fileName   AS CHARACTER FORMAT "x(15)"

FIELD fieldName  AS CHARACTER FORMAT "x(15)"

FIELD fieldsize  as INTEGER FORMAT "&gt;&gt;&gt;9"  LABEL "Field Size"

FIELD sz         AS INTEGER FORMAT "&gt;&gt;&gt;9"

field changesize AS INTEGER FORMAT "&gt;&gt;&gt;9"  LABEL "Change to"

INDEX ix IS PRIMARY UNIQUE fileName fieldName.

RUN FIND_fields.

FOR EACH sqlw NO-LOCK :

DISPLAY sqlw WITH TITLE "Change SQL-WIDTH for this fields" .

END.

DEFINE VARIABLE vlOK AS LOGICAL.

IF CAN-FIND( FIRST sqlw NO-LOCK ) THEN

MESSAGE "Do you wish to update the database?" VIEW-AS ALERT-BOX BUTTONS YES-NO

UPDATE vlok.

ELSE

MESSAGE "Dataserver schema was validated for using WIDTH method." VIEW-AS ALERT-BOX.

IF vlok THEN

DO TRANSACTION:

FOR EACH _file NO-LOCK WHERE NOT _hidden,

EACH _field OF _file WHERE _data-type = "CHARACTER",

EACH sqlw NO-LOCK WHERE FILENAME = _file-name AND fieldName =

_field-name:

ASSIGN _width = changesize.

END.

END.

PROCEDURE FIND_fields:

DEFINE VARIABLE vFieldList  AS CHARACTER NO-UNDO.

DEFINE VARIABLE vSizeList   AS CHARACTER NO-UNDO.

DEFINE VARIABLE vFieldType  AS CHARACTER NO-UNDO.

DEFINE VARIABLE vFieldName  AS INTEGER   NO-UNDO.

DEFINE VARIABLE hBuffer     AS HANDLE    NO-UNDO.

DEFINE VARIABLE hQuery      AS HANDLE    NO-UNDO.

DEFINE VARIABLE hField      AS HANDLE    NO-UNDO.

DEFINE VARIABLE c1   AS INTEGER   NO-UNDO.

DEFINE VARIABLE VarSize     AS INTEGER   NO-UNDO.

DEFINE VARIABLE lv-extent-width AS INTEGER     NO-UNDO.

DEFINE VARIABLE lv-tempdec  AS DECIMAL FORMAT "-&gt;&gt;&gt;&gt;&gt;&gt;&gt;&gt;9.99&lt;&lt;" NO-UNDO.

FOR EACH _file WHERE NOT _hidden

/*AND _file._file-name BEGINS "os_program" */

NO-LOCK:

ASSIGN vFieldList = ''

vSizeList  = ''.

FOR EACH _field OF _file NO-LOCK WHERE _data-type = "CHARACTER":

ASSIGN vFieldList = vFieldList + ',' + _field-name

vSizeList  = vSizeList  + ',' + STRING(INTEGER(_width /*- 2*/))

vFieldType = vFieldType + "," + _field._data-type.

END.

IF vFieldList = "" THEN

NEXT.

/* Ignore the 1st comma in the lists */

ASSIGN vFieldList = SUBSTRING(vFieldList,2)

vSizeList  = SUBSTRING(vSizeList,2)

vFieldType = SUBSTRING(vFieldType,2).

/*   DISPLAY vFieldList FORMAT "x(70)" SKIP */

/*           vSizeList FORMAT "x(70)"       */

/*           vFieldType FORMAT "x(70)".     */

/* Création du buffer de parcours des enregistrements */

CREATE BUFFER hBuffer FOR TABLE _file-name.

CREATE QUERY hQuery.

hQuery:SET-BUFFERS(hBuffer).

hQuery:QUERY-PREPARE("FOR EACH " + _file-name + " NO-LOCK ").

hQuery:QUERY-OPEN().

DISPLAY _file-name WITH FRAME xx .

IF hQuery:GET-FIRST()THEN

REPEAT:

hBuffer = hQuery:GET-BUFFER-HANDLE(1).

DO vFieldName = 1 TO NUM-ENTRIES(vFieldList):

ASSIGN hField  = hBuffer:BUFFER-FIELD(ENTRY(vFieldName,vFieldList))

VarSize = 0 .

/* CHecking valid data for numeric input */

/*         IF LOOKUP(HField:DATA-TYPE, "integer,recid") &lt;&gt; 0 THEN                                       */

/*                                                                                                      */

/*           DO:                                                                                        */

/*                                                                                                      */

/*                                                                                                      */

/*                                                                                                      */

/*             /* message showing field info */                                                         */

/*                                                                                                      */

/*             ASSIGN lv-tempdec = DECIMAL(STRING(hField:BUFFER-VALUE)) NO-ERROR.                       */

/*                                                                                                      */

/*         DISPLAY ENTRY(vFieldName,vFieldList) HField:DATA-TYPE hField:BUFFER-VALUE lv-tempdec. PAUSE. */

/*                                                                                                      */

/*             IF ERROR-STATUS:ERROR THEN                                                               */

/*             MESSAGE "vFieldName    : " ENTRY(vFieldName,vFieldList) SKIP                             */

/*                 "Datatype      : " HField:DATA-TYPE SKIP                                             */

/*                 "Full Width    : " INTEGER(ENTRY(vFieldName,vSizeList)) SKIP                         */

/*                                                                                                      */

/*                 "HField:EXTENT : " HField:EXTENT SKIP                                                */

/*                 "c1            : " c1 SKIP                                                           */

/*                 "Extent Width  : " lv-extent-width SKIP                                              */

/*                 "Variable Size : " VarSize SKIP(1)                                                   */

/*                 "Field Value   : " hField:BUFFER-VALUE                                               */

/*                 VIEW-AS ALERT-BOX INFO BUTTONS OK.                                                   */

/*                                                                                                      */

/*                                                                                                      */

/*                                                                                                      */

/*           END.                                                                                       */

/* If we aren't dealing with a character string then ignore the length checks */

IF ENTRY(vFieldName,vFieldType) &lt;&gt; "CHARACTER" THEN

NEXT.

/* If we are dealing with extents then we need some special code.. */

IF HField:EXTENT &gt; 0 THEN

DO:

DO c1 = 1 TO HField:EXTENT :

/* because the Progress Meta Schema only has one field which

stores the lengths of fields there is only one width value

for extents.  this means that extent widths are the TOTAL

width for all the extents - e.g. width 50 for a field with

extent 5 would mean width 10 for each field (less 2 it seems

for some reason)

So we apply this logic for the extent fields we encounter */

ASSIGN lv-extent-width = (INTEGER(ENTRY(vFieldName,vSizeList))

/  HField:EXTENT) - 2.

IF (LENGTH(hField:BUFFER-VALUE(c1)) &gt;

lv-extent-width) AND

( LENGTH(hField:BUFFER-VALUE(c1)) &gt;

VarSize )

THEN DO :

/* Here we calculate what the Variable size is..

For extents we should multiply it up by the number of extents */

VarSize = (LENGTH(hField:BUFFER-VALUE(c1)) + 2) * HField:EXTENT.

/* message showing extent errors */

/*                  MESSAGE "vFieldName    : " ENTRY(vFieldName,vFieldList) SKIP            */

/*                          "Full Width    : " INTEGER(ENTRY(vFieldName,vSizeList)) SKIP    */

/*                          "HField:EXTENT : " HField:EXTENT SKIP                           */

/*                          "c1     : " c1 SKIP                               */

/*                          "Extent Width  : " lv-extent-width SKIP                         */

/*                          "Variable Size : " VarSize SKIP                                 */

/*                                                                                          */

/*                          LENGTH(hField:BUFFER-VALUE(c1)) "&gt;" lv-extent-width SKIP */

/*                                                                                          */

/*                          VIEW-AS ALERT-BOX INFO BUTTONS OK.                              */

END.

END.

END.

/* Normal field definition */

ELSE

DO:

IF LENGTH(hField:BUFFER-VALUE) &gt; INTEGER(ENTRY(vFieldName,vSizeList)) THEN

DO:

VarSize = LENGTH(hField:BUFFER-VALUE).

END.

END.

/* If the variable size is greater than 0 then this means some fields

have content greater than their field definition */

IF Varsize &gt; 0 THEN

DO:

FIND sqlw WHERE FILENAME = _file-name AND

fieldName = ENTRY(vFieldName,vFieldList)

NO-ERROR.

IF NOT AVAILABLE(sqlw) THEN

DO:

CREATE sqlw.

ASSIGN FILENAME  = _file-name

fieldName = ENTRY(vFieldName,vFieldList)

fieldsize = INTEGER(ENTRY(vFieldName,vSizeList)).

END.

IF sz &lt; varsize THEN

ASSIGN sz = varsize

changesize = varsize + (varsize / 2).

END.

END.

hQuery:GET-NEXT().

IF hQuery:QUERY-OFF-END

THEN LEAVE.

END.

hQuery:QUERY-CLOSE.

DELETE OBJECT hQuery.

DELETE OBJECT hBuffer.

END.  /* FOR EACH _file... */

END PROCEDURE.
</pre>
]]></content:encoded>
			<wfw:commentRss>http://solarpolar.co.uk/checking-a-progress-openedge-database-for-mssql-conversion/feed/</wfw:commentRss>
		<slash:comments>2</slash:comments>
		</item>
		<item>
		<title>Updating a Progress and MSSQL database</title>
		<link>http://solarpolar.co.uk/updating-a-progress-and-mssql-database/</link>
		<comments>http://solarpolar.co.uk/updating-a-progress-and-mssql-database/#comments</comments>
		<pubDate>Tue, 09 Nov 2010 16:58:10 +0000</pubDate>
		<dc:creator>admin21</dc:creator>
				<category><![CDATA[OpenEdge]]></category>
		<category><![CDATA[OpenPeople]]></category>

		<guid isPermaLink="false">http://www.solarpolar.co.uk/?p=422</guid>
		<description><![CDATA[<p>When migrating a Progress database to a MSSQL database I use the following parameters&#8230;</p>
<p>I connect to the database using a differing logical name.  Because our apps are compiled using the logical name of the database we need to supply this logical name to the Schema Holder.</p>
<p></p>
]]></description>
			<content:encoded><![CDATA[<p>When migrating a Progress database to a MSSQL database I use the following parameters&#8230;</p>
<p>I connect to the database using a differing logical name.  Because our apps are compiled using the logical name of the database we need to supply this logical name to the Schema Holder.</p>
<p><a href="http://solarpolar.co.uk/wp-content/uploads/2010/08/pro-sql-migrate.jpg" rel="lightbox[422]" title="Progress to MSSQL migration"><img class="alignnone size-medium wp-image-526" title="Progress to MSSQL migration" src="http://solarpolar.co.uk/wp-content/uploads/2010/08/pro-sql-migrate-300x182.jpg" alt="" width="300" height="182" /></a></p>
]]></content:encoded>
			<wfw:commentRss>http://solarpolar.co.uk/updating-a-progress-and-mssql-database/feed/</wfw:commentRss>
		<slash:comments>0</slash:comments>
		</item>
		<item>
		<title>Progress / OpenEdge Incremental df</title>
		<link>http://solarpolar.co.uk/progres-openedge-incremental-df/</link>
		<comments>http://solarpolar.co.uk/progres-openedge-incremental-df/#comments</comments>
		<pubDate>Fri, 04 Jun 2010 10:04:02 +0000</pubDate>
		<dc:creator>admin21</dc:creator>
				<category><![CDATA[OpenEdge]]></category>
		<category><![CDATA[Progress / OpenEdge Incremental df]]></category>

		<guid isPermaLink="false">http://www.solarpolar.co.uk/?p=379</guid>
		<description><![CDATA[<p>When you want to create an incremental df between two databases you should;</p>

connect to the newer database (appdb)
connect to the older database with diff logical name (oldappdb)
ensure the current working database is the newer (appdb)
create the incremental db from there

<p>Job done!  test</p>
]]></description>
			<content:encoded><![CDATA[<p>When you want to create an incremental df between two databases you should;</p>
<ul>
<li>connect to the newer database (appdb)</li>
<li>connect to the older database with diff logical name (oldappdb)</li>
<li>ensure the current working database is the newer (appdb)</li>
<li>create the incremental db from there</li>
</ul>
<p>Job done!  test</p>
]]></content:encoded>
			<wfw:commentRss>http://solarpolar.co.uk/progres-openedge-incremental-df/feed/</wfw:commentRss>
		<slash:comments>0</slash:comments>
		</item>
	</channel>
</rss>

