<?xml version='1.0' encoding='UTF-8'?><rss xmlns:atom='http://www.w3.org/2005/Atom' xmlns:openSearch='http://a9.com/-/spec/opensearchrss/1.0/' version='2.0'><channel><atom:id>tag:blogger.com,1999:blog-7091790</atom:id><lastBuildDate>Wed, 16 Apr 2008 13:50:35 +0000</lastBuildDate><title>xCase2VPM News</title><description/><link>http://www.prosysplus.net/xcblog/xc2vpmblog.html</link><managingEditor>Hank Fay</managingEditor><generator>Blogger</generator><openSearch:totalResults>13</openSearch:totalResults><openSearch:startIndex>1</openSearch:startIndex><openSearch:itemsPerPage>25</openSearch:itemsPerPage><item><guid isPermaLink='false'>tag:blogger.com,1999:blog-7091790.post-1131762450356858027</guid><pubDate>Wed, 16 Apr 2008 13:47:00 +0000</pubDate><atom:updated>2008-04-16T06:47:50.852-07:00</atom:updated><title>xCase2VPM for xCase 8.2 Released</title><description>&lt;p&gt;Version 1.99.237 of xCase2VPM for xCase 8.2 and VPME9 has been released.&amp;nbsp; It is &lt;a href="http://www.prosysplus.com/products/xcase2vpm_updates.htm" target="_blank"&gt;available here&lt;/a&gt;.&amp;nbsp; The primary purpose of the release is compatibility with xCase8.2.&amp;nbsp; Note that xCase8.1 reintroduces the multiple attributes browser, so if you are upgrading from earlier than that, see the directions below for making sure you have this valuable feature. &lt;/p&gt; &lt;p&gt;Other than compatibility with xCase8.2, this version introduces two important features:  &lt;p&gt;The Append process at the end of an xCase2VPM run is much quicker, because where possible, the table will be copied back, rather than appended. In a few hundred table application, this can cut 10's of minutes off the processing time.  &lt;p&gt;The ability to work around SQL Server's use of Allow Null is now built into the Create Remote DB process. This is important when you want compatibility with VFP-based applications, because it makes the data work just as it does with VFP. VPM takes care of the actual defaults, and whether the fields can be empty(); this eliminates views not working because of NULL FK's, etc. To make this work, run the Create Remote DB process with the settings shown below:  &lt;p&gt;&lt;a href="http://lh4.ggpht.com/HankFay/SAYDhIk9EPI/AAAAAAAAAoc/h24QcRfYzU0/s1600-h/CreateRemoteDB%5B3%5D.png"&gt;&lt;img style="border-top-width: 0px; border-left-width: 0px; border-bottom-width: 0px; border-right-width: 0px" height="84" alt="CreateRemoteDB" src="http://lh6.ggpht.com/HankFay/SAYDhok9EQI/AAAAAAAAAok/A3LetZ3aLzw/CreateRemoteDB_thumb%5B1%5D.png?imgmax=800" width="244" border="0"&gt;&lt;/a&gt;&lt;/p&gt;  </description><link>http://www.prosysplus.net/xcblog/2008/04/xcase2vpm-for-xcase-82-released.html</link><author>Hank Fay</author></item><item><guid isPermaLink='false'>tag:blogger.com,1999:blog-7091790.post-8523915976557705987</guid><pubDate>Mon, 15 Oct 2007 16:24:00 +0000</pubDate><atom:updated>2007-10-15T09:53:20.210-07:00</atom:updated><title>What about VPME9.1X</title><description>We've gotten a couple of questions about VPME9.1X lately: are we going to produce a version of xCase2VPM to go with this version of VPM? In short, the answer is no. The longer answer follows &amp;lt;s&amp;gt;.&lt;br /&gt;&lt;br /&gt;&lt;p&gt;The reasons for our decision are many, some more important than others of course. Here are some, in no particular order of importance. &lt;/p&gt;&lt;ul&gt;&lt;li&gt;With VFP now in an end-of-life cycle, we don't foresee a move by developers to VFP; and since developers moving to VFP were a key component of the VPM market (because VPM is such a huge help in getting going with VFP when doing useful work), we don't foresee an increased market for VPM.&lt;/li&gt;&lt;br /&gt;&lt;li&gt;Our libraries provide the capabilities we need to produce great business applications in VPME9. &lt;/li&gt;&lt;br /&gt;&lt;li&gt;It would be a lot of scut-work changing everything in our libraries to work with VPME9.1x. Nothing has changed in the essence of the processing; but what things are called or where they are located has changed.&lt;/li&gt;&lt;/ul&gt;&lt;br /&gt;&lt;br /&gt;&lt;p&gt;We would love to have a reason to change our decision. &lt;strong&gt;One thing that would help do that would be if VFP applications could be compiled into .Net.&lt;/strong&gt; "What," you say? "We've been told VFP can never run within .Net, and the person telling us that was the Product Manager for VFP!" Well, we'll see how it turns out, but you might want to take a look at a &lt;a href="http://groups.google.com/group/vfpnet-compiler-community-support-group?lnk=iggc"&gt;Community Support Group&lt;/a&gt; for &lt;a href="http://www.etecnologia.net/"&gt;etecnologia.net's VFP.Net compiler&lt;/a&gt;. &lt;strong&gt;If/when Samuel et al. get this thing working, then VPME9.1X will have another life &lt;/strong&gt;(well deserved), and it would make sense for us to proceed with a version of xCase2VPM that implements the interface we have already planned for xCase2&lt;whatever&gt; V2, while converting our libraries to work with VPME9.1X or beyond.&lt;/p&gt;&lt;p&gt;For the moment, we're producing great business applications in VPME9, using our libraries combined with xCase2VPM, and haven't found any reason to do otherwise. We see reasons to be preparing for the future, of course. Right now, what we have is working great. &lt;/p&gt;</description><link>http://www.prosysplus.net/xcblog/2007/10/what-about-vpme91x.html</link><author>Hank Fay</author></item><item><guid isPermaLink='false'>tag:blogger.com,1999:blog-7091790.post-2282268763968186390</guid><pubDate>Wed, 14 Mar 2007 01:27:00 +0000</pubDate><atom:updated>2007-03-13T18:28:49.836-07:00</atom:updated><title>xCase2VPM for xCase 8.1, VPME9 Released</title><description>Come and get it: &lt;a href="http://www.prosysplus.com/products/xcase2vpm_updates.htm"&gt;http://www.prosysplus.com/products/xcase2vpm_updates.htm&lt;/a&gt;&lt;br /&gt;&lt;br /&gt;This takes care of the Browsers issue that resulted from the return of the Multiple Attributes Form.  It has a few other little fixes, I think: when Frank gives me the list, I'll note them here, there and everywhere.&lt;br /&gt;&lt;br /&gt;Directions for how to get your multiple attributes browser back in xCase 8.1, with the ProSysPlus defaults, are given on the download page, above.&lt;br /&gt;&lt;br /&gt;enjoy,&lt;br /&gt;&lt;br /&gt;Hank&lt;br /&gt;&lt;br /&gt;PS: thanks to Frank for figuring out what needed to be done (which turned out to be a) installing over a 7.5 install directly with 8.1, and b) packaging up those browsers for use by xCase2Vpm).</description><link>http://www.prosysplus.net/xcblog/2007/03/xcase2vpm-for-xcase-81-vpme9-released.html</link><author>Hank Fay</author></item><item><guid isPermaLink='false'>tag:blogger.com,1999:blog-7091790.post-116010723916317084</guid><pubDate>Fri, 06 Oct 2006 04:00:00 +0000</pubDate><atom:updated>2006-10-07T18:07:43.550-07:00</atom:updated><title>xCase2VPM V1.99.112</title><description>&lt;p&gt;This version fixes two bugs:&lt;/p&gt; &lt;ul&gt; &lt;li&gt;We added a call to the datasession saver class from PSP Libraries, which was a good thing.&amp;nbsp; I forgot to include it in the build, which was a bad thing.  &lt;li&gt;Somehow someone (Frank will analyze source control files to prove it was me, although I completely deny it, and truthfully cannot remember doing it) broke the code in the Process dialog that filled the Model combobox.&amp;nbsp; Anyway, I fixed it.&lt;/li&gt;&lt;/ul&gt; &lt;p&gt;Time to get back to the next version, don't you think? &amp;lt;s&amp;gt;&lt;/p&gt;</description><link>http://www.prosysplus.net/xcblog/2006/10/xcase2vpm-v199114.html</link><author>Hank Fay</author></item><item><guid isPermaLink='false'>tag:blogger.com,1999:blog-7091790.post-115699415542703339</guid><pubDate>Thu, 31 Aug 2006 03:03:00 +0000</pubDate><atom:updated>2006-08-30T20:29:44.166-07:00</atom:updated><title>xCase2VPM V1.99.74 Released</title><description>This is the last planned release of xCase2VPM for VPME9.  It incorporates, but does not mandate, support of xCase 8.&lt;br /&gt;&lt;br /&gt;Documentation isn't done yet &amp;lt;gd&amp;r&amp;gt; but will be forthcoming.  They will be posted here when available.&lt;br /&gt;&lt;br /&gt;The next version of xCase2VPM will be V2, for VPME9.1, which will be under a new name (PSP4VPM, which will include the PSP Data Dictionary and the PSP Libraries).  The new product will be sold only through a comprehensive subscription package: for existing xCase2VPM users the annual fee for all updates (including PSP4.Net which will appear within the next year), training videos, and support (all through Groove for now) will be $495, with a $100 Early Bird discount.  These subscriptions will be available on the ProSysPlus website when the time comes.&lt;br /&gt;&lt;br /&gt;You can access the &lt;a href="http://www.prosysplus.com/products/xcase2vpm_updates.htm"&gt;downloads here&lt;/a&gt;.&lt;br /&gt;&lt;br /&gt;Enjoy!!!</description><link>http://www.prosysplus.net/xcblog/2006/08/xcase2vpm-v19974-released.html</link><author>Hank Fay</author></item><item><guid isPermaLink='false'>tag:blogger.com,1999:blog-7091790.post-115107189315967613</guid><pubDate>Fri, 23 Jun 2006 14:08:00 +0000</pubDate><atom:updated>2006-06-23T07:11:33.173-07:00</atom:updated><title>European Summer DevCon 2006</title><description>Wondering what's up with xCase2VPM?  Read about it here: http://www.prosysplus.com/blog/2006/06/european-summer-devcon-2006.html !</description><link>http://www.prosysplus.net/xcblog/2006/06/european-summer-devcon-2006.html</link><author>Hank Fay</author></item><item><guid isPermaLink='false'>tag:blogger.com,1999:blog-7091790.post-112451271563529022</guid><pubDate>Sat, 20 Aug 2005 04:38:00 +0000</pubDate><atom:updated>2005-08-19T21:38:35.650-07:00</atom:updated><title>xCase2VPM V2 Live Training in Tampa</title><description>Frank and I have committed to delivering some version of xCase2VPM V2, aka xCase2PSP for VPM, for a demo at the ProMatrix Solutions workshop in Tampa on October 21, and then we’ll do a workshop of our own, actually working with xCase2VPM V2, the next day.&amp;nbsp;&amp;nbsp;Workshop attendees will receive the beta version of xCase2VPM V2. This will be the first release of xCase2VPM V2, and Workshop attendees will be the first to receive it, along with access to the portal site devoted to the beta.&lt;br/&gt;&lt;br/&gt;The Saturday workshop will be the Full Monte of the xCase2VPM Jumpstart: shake it Frank!&lt;br/&gt;&lt;br/&gt;&lt;ul&gt;&lt;li&gt;Installation of xCase2PSP and PSP4VPM (you can’t use xCase2VPM V2 without both components)&lt;/li&gt;&lt;br/&gt;&lt;li&gt;Setting up xCase (not too much to do: we no longer add attributes to xCase)&lt;/li&gt;&lt;br/&gt;&lt;li&gt;Quick Demo to prove it works! (Developed directly in SQL Server)&lt;/li&gt;&lt;br/&gt;&lt;li&gt;Setting up xCase2PSP Advanced: your own attributes and code generation&lt;/li&gt;&lt;br/&gt;&lt;li&gt;Working with Entities: all the features you liked in V1&lt;/li&gt;&lt;br/&gt;&lt;li&gt;Generated vs. xCase Views: why you will rarely need xCase views&lt;/li&gt;&lt;br/&gt;&lt;li&gt;Working with Fields: all the features you liked in V1&lt;/li&gt;&lt;br/&gt;&lt;li&gt;Working with Validation Rules&lt;/li&gt;&lt;br/&gt;&lt;li&gt;Working with Business Rules&lt;/li&gt;&lt;br/&gt;&lt;li&gt;Bonus Session:&amp;nbsp;&amp;nbsp;Moving your model to MM.Net using PSP4MM.Net&lt;/li&gt;&lt;/ul&gt;&lt;br/&gt;When I went back to the xCase model for V2, I was interested to see that it had been started in 2003: and that I still like the ideas in it. &amp;lt;g&amp;gt;&amp;nbsp;&amp;nbsp;Ideas like the ability for users to add their own MetaData attributes to any object, and direct how those new attributes are used.&amp;nbsp;&amp;nbsp;&lt;br/&gt;&lt;br/&gt;The interface will be in .Net, which was not in the original plan.&amp;nbsp;&amp;nbsp;In that time, .Net has gotten better, MM.Net has matured, and Infragistics controls have progressed.&amp;nbsp;&amp;nbsp;So, Frank and I decided to bite the bullet and develop the interface using MM.Net and Infragistics.&amp;nbsp;&amp;nbsp;On the backend will be a COM object written in VPME9 using the PSP Libraries.&amp;nbsp;&amp;nbsp;Which we will rewrite in VPME91 once we get V2 working.&amp;nbsp;&amp;nbsp;Why a VPM COM object?&amp;nbsp;&amp;nbsp;Because nothing does data like Fox.&amp;nbsp;&amp;nbsp;And if Anders Hejlsberg (creator of the CLR and C#, and currently adding data access improvements to C#) doesn’t have a VFP guru looking over his shoulder and shaking his/her head in dismay at his lack of data experience, well, it’s all our loss.&lt;br/&gt;&lt;br/&gt;This is the only live training Frank and I have scheduled at this point, since we find the Online Videos and Support format to be so effective.&amp;nbsp;&amp;nbsp;But live training for something like this is exciting for everyone.&amp;nbsp;&amp;nbsp;And this stuff will blow people away.&amp;nbsp;&amp;nbsp; I’m excited, and I’ve been thinking/working on this over a period of 2 years.&lt;br/&gt;&lt;br/&gt;You can sign up for the course on the &lt;a href="http://www.promatrix.com/training/october_2005.htm"&gt;ProMatrix training site&lt;/a&gt;.</description><link>http://www.prosysplus.net/xcblog/2005/08/xcase2vpm-v2-live-training-in-tampa.html</link><author>Hank Fay</author></item><item><guid isPermaLink='false'>tag:blogger.com,1999:blog-7091790.post-111587704033823054</guid><pubDate>Thu, 12 May 2005 05:50:00 +0000</pubDate><atom:updated>2005-05-11T22:50:40.363-07:00</atom:updated><title>xCase2VPM 1.99 for xCase 7.5 and VPME9</title><description>As the title says... get it at &lt;a href="http://www.prosysplus.com/products/xcase2vpm_updates.htm"&gt;the update site&lt;/a&gt;.&lt;br /&gt;&lt;br /&gt;This will be the last version for VPME9 (there might be builds to correct bugs, but there will be no enhancements leading to major or minor version changes).  The reason for this is VPME91, which will be released in a few days.  Here are our (Frank and Hank) plans for VPME91 and xCase2VPM, and the reasons why:&lt;br /&gt;&lt;br /&gt;&lt;em&gt;First,&lt;/em&gt; VPME91 changes the way a lot of things work: we need to take advantage of these changes.  This includes how business rules are implemented, and the ability to develop directly into client-server databases.&lt;br /&gt;&lt;br /&gt;&lt;em&gt;Second,&lt;/em&gt; we need to make xCase2VPM easier to use in two areas: User Interface (UI) and speed (of generation after model changes).  This means a) we build our own interface, using xCase for the things it does best (design entities, fields, relations, indexes, views), while using our interface for everything else.  It also means incremental generation (and avoiding generation in many cases, through the uses of dynamic cursoradaptors) of xCase model into VPM and into the actual data.&lt;br /&gt;&lt;br /&gt;&lt;em&gt;Third,&lt;/em&gt; as a result of First and Second, above, Frank and I confirmed over the past two days our earlier notions that we would put our information that was additional to VPM into separate data tables that would be distributed with the application.  This was an early thought we had, and became even clearer when we realized that to take advantage of some of the new power in VPME91, we would have to extend the VPM metadata through additional child tables.  &lt;br /&gt;&lt;br /&gt;So, that all said, we are looking at 1) an entirely new xCase2VPM: it will be a VPM application; and 2) a refactoring of the PSP Libraries into the VPME91 context.&lt;br /&gt;&lt;br /&gt;The new xCase2VPM will be twice as efficient as the old one if you are working on small to medium models; it will be even more efficient if you are working on large models.&lt;br /&gt;&lt;br /&gt;The new PSP Libraries will give you unbelievable power and control over what happens in your VPM programs.  ProMatrix has gotten even more stuff right, and we're in a position to use what they have delivered to give you even more.  Well, to be honest, it's really for us (as I told Frank and breakfast today, "we've never done anything just for the xCase2VPM users that we didn't want anyway, so why start now?" &amp;lt;g&amp;gt; ), but everyone gets to benefit.&lt;br /&gt;&lt;br /&gt;So, there will be an upgrade price for xCase2VPM, which in the tradition of such things will be 60% of the current price, which we expect to stay the same ($699).  We have, however, added two ways to get free xCase2VPM upgrades: the two video+online Training Subscriptions which we have created from the 4 courses (xCase2VPM Jumpstart; ActiveX/COM/.Net; VPM2Web; PSP Libraries) currently described on our website and offered for purchase on the ProMatrix website.&lt;br /&gt;&lt;br /&gt;The two courses will be xCase2VPM Jumpstart, which will be exactly what it is now.  The other will be a combination of all 4 courses into a reconfigured PSP Libraries.  The current courses are online videos, support through Groove (you buy the Groove from Groove.net, Professional version), and occasional online sessions to make new videos.  There will be two Groove spaces: the xCase2VPM Jumpstart space, and the PSP Libraries space.  The latter will handle all non-xCase2VPM matters.  Frankly, it was too tough to separate out the PSP Libraries issues from COM/.Net and from VPM2Web.  Those who sign up for the PSP Libraries support, will get both Groove spaces.&lt;br /&gt;&lt;br /&gt;&lt;strong&gt;Pricing for the training has decreased&lt;/strong&gt; (that is not a typo -- we want people to use this stuff, because the more people that use it, the better it becomes as a result of feedback):&lt;br /&gt;&lt;br /&gt;&lt;strong&gt;xCase2VPM Jumpstart:&lt;/strong&gt; $499 ($299 within 30 days of purchasing xCase2VPM); $199 annual renewal.&lt;br /&gt;&lt;br /&gt;&lt;strong&gt;PSP Libraries:&lt;/strong&gt; $1099 ($899 within 30 days of purchasing xCase2VPM); $499 annual renewal.&lt;br /&gt;&lt;br /&gt;The xCase2VPM Jumpstart course gets a Library refresh once per year.&lt;br /&gt;&lt;br /&gt;The PSP Libraries course gets Library refreshes as needed (we intend to tie in the Change Log with incremental refreshing).&lt;br /&gt;&lt;br /&gt;So that's the news from Southwest Florida, where I put down the convertible top in the hope that Frank will get something of a tan before he returns to Weert, NL.</description><link>http://www.prosysplus.net/xcblog/2005/05/xcase2vpm-199-for-xcase-75-and-vpme9.html</link><author>Hank Fay</author></item><item><guid isPermaLink='false'>tag:blogger.com,1999:blog-7091790.post-109798334302459749</guid><pubDate>Sun, 17 Oct 2004 03:22:00 +0000</pubDate><atom:updated>2004-10-16T20:22:23.023-07:00</atom:updated><title>Version 1.90.176 Released</title><description>The newest version of xCase2VPM is available &lt;a href="http://www.prosysplus.com/products/xcase2vpm_udpates.htm"&gt;on the update site&lt;/a&gt;.&lt;br /&gt;&lt;br /&gt;This version is consistent with the recently released version of the ProSysPlus Libraries (made available as an update for those enrolled in the PSP Libraries subscription).&lt;br /&gt;&lt;br /&gt;The xCase Search and Replace functionality has been honed in this release.  It is also able to be used with VFP9 data types (although it has not yet been modified to run with xCase 7.5, which was just released).</description><link>http://www.prosysplus.net/xcblog/2004/10/version-190176-released.html</link><author>Hank Fay</author></item><item><guid isPermaLink='false'>tag:blogger.com,1999:blog-7091790.post-109012902150535633</guid><pubDate>Sun, 18 Jul 2004 05:37:00 +0000</pubDate><atom:updated>2004-07-19T17:36:29.800-07:00</atom:updated><title>xCase2VPM 1.90.141 Major New Features</title><description>I probably should have bumped up the secondary version number, with the new features introduced into this build:&lt;br /&gt;&lt;br /&gt;&lt;ul&gt;&lt;br /&gt;&lt;li&gt; &lt;strong&gt;Compatibility with VFP9's new data types&lt;/strong&gt; (xCase is modified by xCase2VPM, automatically, to make this work). Frank had to have this to play with VFP9, so he just went ahead and did it. (Yes, we know, VPM doesn't run with VFP9; but of course Frank got that working too, with a workaround available to those who are in the PSP Libraries video course support Groove space.)&lt;br /&gt;&lt;/li&gt;&lt;li&gt; &lt;strong&gt;Search and Replace&lt;/strong&gt;: a utility written by &lt;strong&gt;David LeMesurier&lt;/strong&gt; which allows you to Search and Replace within your xCase model.&lt;br /&gt;&lt;/li&gt;&lt;li&gt;&lt;span style="font-weight: bold;"&gt; Team Data Structure Updates&lt;/span&gt;: two processes that allow Team members to update their data structure without running xCase2VPM, but while still retaining their personal test data.&lt;br /&gt;&lt;/li&gt;&lt;/ul&gt;&lt;br /&gt;&lt;br /&gt;As always, there are a number of bug fixes: I make them, Frank fixes them, if I'm lucky. &amp;lt;s&amp;gt;&lt;br /&gt;&lt;br /&gt;Enjoy,&lt;br /&gt;&lt;br /&gt;Hank</description><link>http://www.prosysplus.net/xcblog/2004/07/xcase2vpm-190141-major-new-features.html</link><author>Hank Fay</author></item><item><guid isPermaLink='false'>tag:blogger.com,1999:blog-7091790.post-108865315230338776</guid><pubDate>Thu, 01 Jul 2004 03:37:00 +0000</pubDate><atom:updated>2004-06-30T20:39:12.303-07:00</atom:updated><title>VFP9 Compatible Version Coming</title><description>For those playing with the &lt;a href="http://msdn.microsoft.com/vfoxpro"&gt;VFP9 Public&lt;br /&gt;Beta&lt;/a&gt;, it sure would be nice to have a copy of xCase and xCase2VPM that were compatible with the new features, wouldn't it?&amp;#160; Well, Frank Camp has been hard at work (well, play, but serious play &amp;lt;s&amp;gt;) making this possible.&amp;#160; All I have to do it put the pieces together now.&amp;#160; It'll be a few days.</description><link>http://www.prosysplus.net/xcblog/2004/06/vfp9-compatible-version-coming.html</link><author>Hank Fay</author></item><item><guid isPermaLink='false'>tag:blogger.com,1999:blog-7091790.post-108865274490684203</guid><pubDate>Thu, 01 Jul 2004 03:32:00 +0000</pubDate><atom:updated>2004-06-30T20:44:30.226-07:00</atom:updated><title>Version 1.90.118 </title><description>&lt;strong&gt;Fixes:&lt;/strong&gt;&lt;/p&gt;&lt;ul&gt;   &lt;li&gt;      &lt;strong&gt;Quick RI &lt;/strong&gt;had an obscure bug, which those who reported it to me over      the last year, but which I couldn't replicate here, will be overjoyed to learn has      been squashed.&lt;/li&gt;   &lt;li&gt;      &lt;strong&gt;Field-based Upper Candidate indexes&lt;/strong&gt; were not being created as Upper.      This is the nth time this has been fixed: may it be the last.&lt;/li&gt;   &lt;li&gt;      &lt;strong&gt;AcolScan() &lt;/strong&gt;has been replaced through xCase2VPM, in line with it being      deprecated in the PSP Libraries.&lt;/li&gt;   &lt;li&gt;      &lt;strong&gt;Custom Compound Fields&lt;/strong&gt; were not always enrolled correctly.&lt;/li&gt;&lt;/ul&gt;&lt;p&gt;   &lt;strong&gt;Enhancements:&lt;/strong&gt;&lt;/p&gt;&lt;ul&gt;   &lt;li&gt;      &lt;strong&gt;ParentPKValue Views&lt;/strong&gt; with multiple parent relations are now easier      to find: the FK index expression is now specified in the Comments field of the Entity,      on the Properties page of the Entity in the Data Manager.&lt;/li&gt;&lt;/ul&gt;</description><link>http://www.prosysplus.net/xcblog/2004/06/version-190118.html</link><author>Hank Fay</author></item><item><guid isPermaLink='false'>tag:blogger.com,1999:blog-7091790.post-108537336045198025</guid><pubDate>Mon, 24 May 2004 04:33:00 +0000</pubDate><atom:updated>2004-05-23T21:36:00.453-07:00</atom:updated><title>Replacing the xCase2VPM Announcements Maillist</title><description>In the past, I've hesitated to besiege people with announcements about each and every build posted on the updates site.  Because this is a less intrusive medium, the new policy will be that each build placed on the updates site will be noted here.</description><link>http://www.prosysplus.net/xcblog/2004/05/replacing-xcase2vpm-announcements.html</link><author>Hank Fay</author></item></channel></rss>