>

SCAN FOR ordnmb=m.ordlin.ordnmb AND lnline=m.ordlin.lnline

>
>Definitely agree that SCAN FOR is preferable to SET FILTER, SCAN - though sometimes if code is in 3rd-party resources whose next update will overwrite any local edits, or from decades ago before all current features got added to VFP- then it may be rational to declare "if it ain't broke, don't fix it."
>
>FWIW, in 2021 and if you ever intend to use VFP C++ Compiler: there's a difference between
>
>

nStyle_Stone_Price=0
>nOrdLin_Var_Price = 0
>nDiamValu = 0
>nClrValu = 0
>nProtected = 0

>
>- and -
>
>

store 0 to nStyle_Stone_Price, nOrdLin_Var_Price, nDiamValu, nClrValu, nProtected

>
>By default, the first version will have the variable names obfuscated; the second will not.
>
>You could cause the second version to obfuscate by including comment attributions:
>
>

* nStyle_Stone_Price=
>* nOrdLin_Var_Price =
>* nDiamValu = 
>* nClrValu = 
>* nProtected =

>
>Just something to think about! ;-) - J

I don't much see the point of switching to that. For one, it's from China and from the 3D printing community, I am really not looking forward to having the head programmer under the CCP thumb. I'm really on the lookout for a framework that can let me be productive as I was with MaxFrame. Starting to think I'll just have to build those features into .Net Core.

Just yesterday I tried to get permission to use transactions in part of a legacy application - one that has no transactions, is using sql server, but often drags down entire tables, twice as many views as needed, etc, etc. It's not anything to do with how often a crash happens, I said. It's about standards and best practices - but it's still a struggle.

What I did with MaxFrame evolved from using it for several projects and teaching 50ish week-long here's how to use MaxFrame to start building your app - off the top of my head. I shared this idea with Drew Speedie and other MaxFrame users. It's crazy fast, it requires very little code and give users abilities I've always wanted to see in apps that are slow, awkward, broken - which seems to be most of them. Drew called it boring because the UI is completely homogenous. As you've seen recently, I've had less and less desire to share. It's like talking to anti-vaxxers. I even went to a Microsoft support forum to ask them why they don't diff the exe, and the regular peanut gallery types started poo-pooing, until a MS tech jumped in and said it's a good idea. Drew used to do a single form in 15 minutes. I got to doing 2 forms in 15 minutes, but because they interacted, I ended up not needing to build other forms that would normally support these two.

I explained part of it to Dragan once and he got it. Others didn't. It took a while to make VMP do it. I have not seen anything like it. Clients where I used it asked me what they need their old programmers for if I can build like that? One user started up the stairs to get a copy from a file, I reproduced the original just by specifying the date range as part of the form's query utility. Finally proved to the users, they finally had the system they wanted.