I was already doing that with the FP distribution tool kit from FP Dos days and working with a custom db that the law firm had that was proprietary to the system the firm had. They made an ODBC driver and I got data in and out of it 93-96.
Mike, you see every problem as a nail and you apply the VFP hammer at with ease as well as speed. If you did the same thing with your backend of choice and allowed the DB to do the tasks it does so well and you just task them from VFP I'd say you are a multi-tiered developer. When you have to grab data from any system off of the web you would usee the right tools to do that as well, HTML & CSS or python. I have to get international bank exchange rates on a monthly basis. It is a simple grab but I don't use my database to do that. On Fri, Jun 28, 2019 at 10:00 AM MB Software Solutions, LLC < [email protected]> wrote: > Hi Steve, > > I don't doubt your method is super secure, but this shows a difference > of approaches: you code heavily in the backend DB and as a result > everything is very rigid. If things were to need to be changed to a > different backend, then your project is most definitely a > heavier/longer/more-expensive job than mine. Granted, that scenario may > never come to be for many projects, but ever since I saw Bob Lee > demonstrate VFP using MySQL at the 2003 WhilFest conference, I've > applied that 3-tier (UI/BizObj/DataObj) approach to all of my > solutions. I still do some programming in the backend database for > triggers and some minor functions and stored procedures, but most of my > data code is in the DataObj tier of my app. I have found that it helps > me to be very nimble/agile with projects. > > You're the large mass army; I'm the quick-strick special teams. Both can > do the job and each has their strengths. ;-) > > > On 6/28/2019 10:27 AM, Stephen Russell wrote: > > I am backing off of licenses for SQL Enterprise down to Standard for 2/3 > of > > all my SQL Server usage in my new deployments. Use to have a total of 96 > > cores running Ent. and now seeing if we can only use 30. Having virtual > > guests instead of a single bad ass box makes this a lot easier to do. > > > > Dynamic SQL can burn you. > > > > > https://www.cnet.com/news/sony-playstation-site-victim-of-sql-injection-attack/ > > > > > > Making a stored procedure is common sense. Why you cannot see the beauty > > of it for long term source code is lost on me. Say you make a change to > a > > table. You can easily find every sproc that referenced that table with > > this statement and miss all that you have fixed: > > declare @text varchar(50) > > , @stringtosearch varchar(100) > > , @comment varchar(150) > > > > > > set @text = 'Warehouse' > > set @comment ='%WarehouseChange fixed%' > > > > SET @stringtosearch = '%' +@text + '%' > > > > SELECT Distinct SO.Name > > FROM sysobjects SO (NOLOCK) > > INNER JOIN syscomments SC (NOLOCK) on SO.Id = SC.ID > > AND SO.Type = 'P' > > AND SC.Text LIKE @stringtosearch > > and SO.id not in > > (select distinct SO1.ID > > FROM sysobjects SO1 (NOLOCK) > > INNER JOIN syscomments SC1 (NOLOCK) on SO1.Id = SC1.ID > > AND SO1.Type = 'P' > > AND SC1.Text LIKE @comment) > > > > ORDER BY SO.Name > > > > You can then cross reference every place that the table was used and see > if > > you need to tweak the data access to include the change you just made to > > the column. > > > > We just got handed an oh by the way that hits a major focus on how we > track > > sales. We use to give all sales to the plant that made them, which makes > > sense. Over time we have created warehouses in areas of the country to > hold > > product for delivery to a customer rich area. Sure the ERP already did > > this but the early reporting team never saw that value. > > > > All of these changes are only in our BI/reporting system or our customer > > portal. We have to identify over 1000 sprocs to validate that nothing > > needs to be done here and only 150 really need to be altered. > > > > How would you find that in your prgs? I use the power of the db > engine > > to do a lot of things like this for me. > > > > > > On Thu, Jun 27, 2019 at 6:16 PM MB Software Solutions, LLC < > > [email protected]> wrote: > > > >> On 6/27/2019 6:39 PM, Paul H. Tarver wrote: > >>> Give me a little credit for being a better programmer than that. > >> > >> C'mon, Paul -- it's mega-million$ $teve we're talking about here. Mr. > >> Deep Pockets with SQL Server blinders on usually with only Stored > >> Procedures being the only viable safe option. > >> > >> lol > >> > >> > >> > >> --- > >> This email has been checked for viruses by Avast antivirus software. > >> https://www.avast.com/antivirus > >> > >> [excessive quoting removed by server] _______________________________________________ Post Messages to: [email protected] Subscription Maintenance: http://mail.leafe.com/mailman/listinfo/profox OT-free version of this list: http://mail.leafe.com/mailman/listinfo/profoxtech Searchable Archive: https://leafe.com/archives This message: https://leafe.com/archives/byMID/cajidmy+l8l5ppkaulhnj1fjh24hqueyv1mrserhnty7m4tx...@mail.gmail.com ** All postings, unless explicitly stated otherwise, are the opinions of the author, and do not constitute legal or medical advice. This statement is added to the messages for those lawyers who are too stupid to see the obvious.
