Hi Marcia,

Like in everything else, there are many ways to skin the cat, and once you get to know the tools available for SF (BOM,  DDT, RBS) and use them then you will see the light at the end of the tunnel These tools are design with automation in mind, so the application can take care of itself automatically or with your assistance but being easy on your part.   Please don't show this post to Andy

Edhy Rijo

Hi Charles.

>> Don't know if you looked at the DDT very much, but the SMO approach to schema changes - and the ability to easily add that into the app ala Stonefield update is pretty impressive.  <<

< rof,l > and < lol >!!!! With Andy's involvement in this project as DBA, you can well imagine that his reastion would be "over my dead body!". When we were watching things in SQL Profiler, he was very upset at seeing the framework make direct calls to SP_ExecuteSQL.

I think here you'll find the biggest surprises are in the area of "Oh my god, they are already handling that" (e.g. bubbling up the sp errors, presenting a wizard to handle connection if one is not already established etc.) Wait till you see the message service and localization stuff. Roll based security very cool as well. Don't know if you looked at the DDT very much, but the SMO approach to schema changes - and the ability to easily add that into the app ala Stonefield update is pretty impressive.



I hope after a year of using this you come to the training class next year (and bring Andy) I think you'll get a real kick out of Trent and Ben and the rest of the crew. (would really enjoy hearing Andy and Ben get into SQL esoterica )



Anyway, I look forward to your insights and contributions here as I know you will bring a lot of experience and general common sense to using the product.

Hi Charles.

Well, having written my own VFP framework, I understand all too well that all frameworks make assumptions and in order to use the framework effectively, one has to understand what those assumptions are That is the learning curve and it can't be avoided.

I for one am very glad to see you here. I think we all agree good frameworks only get better when knowledgable, experienced and ... intense users bang on it and ask questions.



As I said before, I think the more you get to know the framework - and especially the Microfour folks - the more you are going to be delighted.

Hi Dustin.

>> As mentioned in the previous post, I'll include a note in the pertinent topics regarding SET NOCOUNT ON for the next release. Sorry for the confusion! <<

No worries I really am not rying to beat you up on this one. All in all, I am happy with my choice to go with Strataframe. It's a big product, so I expect to get a few bruises on the learning curve

Marcia,

As mentioned in the previous post, I'll include a note in the pertinent topics regarding SET NOCOUNT ON for the next release. Sorry for the confusion!

Hello Stataframe team Member:

>> you can't use the SET NOCOUNT ON command at the top of your sproc (StrataFrame uses the count to determine the number of rows affected.) <<

It would be awfully nice if this were actually in the Stataframe documentation. Since my husband is a SQL Server DBA, he writes all of my stored procedures. I just happened to find this accidentally after a day of pulling my hair out for no reason.

Since best practice in SQL Server is to SET NOCOUNT ON at the beginning of every stored procedure to improve performance and to use @@RowCount to return the row count, my husband does not understand why the framework relies on NOCOUNT being off.

Marcia

No problem, glad you got it working

Dustin, It was mine SP. SET NOCOUNT ON was the probelm.Thank you