Point taken. Don't mean to belabor the point. Just pointing out that in a tutorial saying 'put in this code' creates confusion when the code references fields that are not the fields in the sample data being used. I am sure this particular issue will seldom arise as the field names probably won't change again. Having written a lot of framework tutorials I just always found it was less work to change the code in the instructions than to keep explaining to people that the data structure doesn't match the instructions

If you are referring to the pictures, this is not something we are going to change for each version.  This is to illustrate that the StrataFrame references need to be added.  If you open up the provided source code that comes with the framework for each of the tutorials you will see that these references have been changed and that the projects have the most recent references.  We will look at changing the text to further illustrate this point.  But we do not have plans to change the documentation images everytime we change the version of the framework as this would become very cumbersome and dramatically protract releases.

Sorry, I was actually referring to Strataframe and the Winforms VB tutorial.



( do a search in Help and you'll see what I mean )



Not at all a big deal if somebody knows its there but is a little confusing if you tend to cut and paste code when working through the tutorials.



( sorry, I'm a compulsive proof-reader )



Just wanted to mention it in case other newbies weren't aware those field names had changed in the sample data ...

We are not in control of StrataTrain, but I will pass this along.  Sorry for any trouble.

( see post "For current or potential Stratatrain users" in Enhancement Requests )



Suggest hunting down and killing any vestigial references to old field names in sample data ( so far I only know of the two mentioned above ) in Help and samples. Obviously no big deal if you know they are there, but very frustrating for extremely new users. As mentioned in the other thread, BO Mapper will fix partial classes but the form control properties will not be automatically changed in samples.



( just to save the slow witted like me from inundating support with stupid questions )