ProFox May 2018

profox@leafe.com

39 participants
46 discussions

Re: String Reference to Object
by Gene Wirchenko 25 Feb '20

25 Feb '20

At 11:07 2018-02-15, Gene Wirchenko <genew(a)telus.net> wrote: >At 10:57 2018-02-15, "Fernando D. Bozzo" <fdbozzo(a)gmail.com> wrote: >>To talk with an example, if you have this: >> >>oObj = createobject("custom") >>reference = "oObj" >> >>The you have at least 3 options: >> >>1) The way you know => &reference..referredto >> >>2) Using evaluate => =Evaluate(reference + ".referredto") >> >>3) My preferred: Caching the object and then using it: >> >>oRef = Evaluate(reference) >>? oRef.refered1 >>? oRef.refered2 >>... > > I was hoping to avoid evaluate(), but your third way makes > sense. I will check if it works in all the contexts I am thinking > of. (I was using "object" and "reference" rather loosely.) Unfortunately, it does not work in my usual use case: as an alias. Example: use ccli where=evaluate("ccli") && Nope ? where.clcode Sincerely, Gene Wirchenko

9 9

Google API for Geocoding ... Again
by Dave Crozier 04 Feb '19

04 Feb '19

Fellow Gentlemen, I posted a request about doing geocoding requests to receive back a Lat/Long dataset for various addresses a few weeks ago and now find that Google do in fact provide a Geocoding service: https://developers.google.com/maps/documentation/geocoding/start The responses back from the requests are all JSON from a Java Script API run by Google. I have looked over Rick's Westwind site to try and get a start on using this method to get back a JSON response but seem to be getting nowhere fast. Anyone got any ideas on a simple & neat way of retrieving this data back using VFP programmatically? Either that or anyone know a free Geocoding site that would handle up to 100 name and address calls per day ideally by sending a text file and receiving one back which could be automated from the VFP end. Never even looked at Web services in anger before so it all seems a little baffling and terribly long winded at the moment unless I am missing something obvious. Note I don't want to have to drop into an intermediate program/language to accomplish this, if possible. Dave

9 23

[NF] Maybe THIS is the year for Linux....lol
by mbsoftwaresolutions＠mbsoftwaresolutions.com 09 Aug '18

09 Aug '18

http://tech.firstpost.com/news-analysis/the-great-linux-game-25-years-and-m… How many times have they said "Maybe this year!?!?!"

4 6

[NF] Best Practices for collaborative sharing of information
by mbsoftwaresolutions＠mbsoftwaresolutions.com 15 Jun '18

15 Jun '18

The Corporate gig has tasked me with looking into a way for several similar organizations to communicate and share with each other things are the related to the success of all of them; a collaborative sharing of ideas, best practices, information, etc. to help the (healthcare) product as a whole. I have advised against a listserve as I don't feel that's friendly enough for sharing materials/files/stories. I'm believing a forum would be best. Would appreciate your thoughts. Thanks, --Mike

11 28

Re: Fun with date calculations in VFP
by Gene Wirchenko 31 May '18

31 May '18

At 08:30 2018-05-18, mbsoftwaresolutions(a)mbsoftwaresolutions.com wrote: >On 2018-05-16 18:02, Ted Roche wrote: >>LastDayOfMonth() or LDOM back in my 8.3 days, was always a popular request: >>http://fox.wikis.com/wc.dll?Wiki~FindingTheLastDayOfTheMonth~VB > > >Ed Leafe had shared a ton of date functions for VFP years >ago. Here's what I have in my framework from Ed: [snipped code] I want to play, too! Here are my date functions. Some are duplicates. Some are specific to my app. The routine that will be most likely appreciated is megomonth(). ***** Start of Included Code ***** * * Subsection: Date Functions * * Many of these functions return date values, but many do not. * maybelom * Adjust Date to Last of Month? * Last Modification: 2000-06-22 * * Some dates near the end of the month should be adjusted to the last * day of the month. Adjustment is at operator discretion. "near" means in * the last five days. * * Do nothing to null or blank dates. procedure maybelom lparameters thedate, datename if isnull(thedate) or thedate={} return thedate endif local eom eom=lastdom(thedate) if day(eom)-day(thedate)<5 and thedate#eom && Yes, "<" not "<=". clear typeahead yesno=messagebox(; datename+" is close to but not the last day of its month."+CHRCR+; "Adjust it to be the last day of its month?",; MB_YESNO+MB_DEFBUTTON1,"Please confirm")=IDYES if yesno return eom else return thedate endif else return thedate endif endproc * ymendtod * Make an End of Month Date from Year, Month * Last Modification: 2005-10-25 procedure ymendtod lparameters theyear, themonth local thedate if theyear#9999 or themonth#12 thedate=date(theyear,themonth,1) thedate=gomonth(thedate,1)-1 else thedate=date(9999,12,31) && Handle this extreme case. endif return thedate endproc * lastdom * Return Last Day of Month * Last Modification: 2001-01-21 procedure lastdom lparameters thedate * * The checking for an empty date is not needed in VFP 6, but better safe than * sorry. if empty(thedate) return thedate endif return ymendtod(year(thedate),month(thedate)) endproc * firstdom * Return First Day of Month * Last Modification: 2001-01-21 * * The checking for an empty date is not needed in VFP 6, but better safe than * sorry. procedure firstdom lparameters thedate if empty(thedate) return thedate endif local daysoff daysoff=day(thedate)-1 return thedate-daysoff endproc * megomonth * Month End Handling Version of gomonth() * Last Modification: 99-05-04 * * If thedate is the last day of the month, make sure that the return value is * also the last day of its respective month. This adjustment is required * where thedate is the last day of a month that is shorter than that of the * return value's month. Example: * Call Return Value * ---- ------------ * gomonth({^1999.02.28},-2) {^1998.12.28} * megomonth({^1999.02.28},-2) {^1998.12.31} procedure megomonth lparameters thedate, moveby if thedate=lastdom(thedate) return lastdom(gomonth(thedate,moveby)) else return gomonth(thedate,moveby) endif endproc * goyear * Adjust Date by Years * Last Modification: 2013-01-21 * * If February 28 is adjusted to a leap year, the return date will be February * 28 if thedate is in a leap year and Febrauary 29 if it is not. IOW, if * thedate is at the end of the month, the return date will also be so. procedure goyear lparameters; thedate,; && D: base date theoffset && N: offset in years; can be negative if empty(thedate) return thedate endif local newdate newdate=gomonth(thedate,12*theoffset) if thedate=lastdom(thedate) newdate=lastdom(newdate) endif return newdate endproc * dtocyymm * Convert Date to Month Character Display * Last Modification: 2000-01-10 * * This routine is meant to generate two year digits. procedure dtocyymm lparameters thedate local dtosdate, char dtosdate=dtos(thedate) char=substr(dtosdate,3,2)+"."+substr(dtosdate,5,2) return char endproc * dtocw * dtoc() Wrapper * Last Modification: 99-12-28 * * This routine shows that the particular call has been dealt with w.r.t. Y2K * and the intent is that the call should results in year digits according to * the setting of set century. procedure dtocw lparameters thedate return dtoc(thedate) endproc * dtocy2 * dtoc() Generating *Two* Year Digits For Sure * Last Modification: 99-12-28 * * This routine shows that the particular call has been dealt with w.r.t. Y2K * and the intent is that the call should results in two year digits * regardless of the setting of set century. * * This routine is intended for use in reports where the full four-digit year * would take up needed space. procedure dtocy2 lparameters thedate local fcentury, chardate fcentury=set("century") set century off chardate=dtoc(thedate) set century &fcentury return chardate endproc * dtocy4 * dtoc() Generating *Four* Year Digits For Sure * Last Modification: 99-12-28 * * This routine shows that the particular call has been dealt with w.r.t. Y2K * and the intent is that the call should results in four year digits * regardless of the setting of set century. * * This routine is intended for use where the full four-digit year is * required. procedure dtocy4 lparameters thedate local fcentury, chardate fcentury=set("century") set century on chardate=dtoc(thedate) set century &fcentury return chardate endproc * dispyymm * Create a String of YY-MM Format from a Date * Last Modification: 2002-09-25 * * This routine is intended to generate a two-digit year. procedure dispyymm lparameters thedate return; right(str(year(thedate)+100),2)+"-"+right(str(month(thedate)+100),2) endproc * datespelled * Create Spelled-Out Date * Last Modification: 2007-04-03 * * Precondition: A date to spell out. * Postcondition: Returns the date spelled out * <full month name> <day>, yyyy * This is almost the same as mdy() with set century on, but mdy() creates * two-digit day strings as in "April 03, 2007". It also returns "*bad date*" * for an empty date. This routine does neither. procedure datespelled lparameters; thedate && D: the date to spell out if empty(thedate) return "" else return cmonth(thedate)+" "+transform(day(thedate))+", "+; transform(year(thedate)) endif endproc * uctdatestr * Convert Date to UCT Date String * Last Modification: 2015-08-17 * * UCT date string format is YYMMDD. procedure uctdatestr lparameters; thedate && D: date to convert if empty(thedate) return space(6) else return right(dtos(thedate),6) endif endproc * forthedatesstr * Generate "For the dates" String * Last Modification: 2015-06-17 * * Generates strings depending on datelow and datehigh being empty or not: * "For all dates" if datelow and datehigh are both empty * "For the dates from 99.99.99 on" if only datehigh is empty * "For the dates up to 99.99.99" if only datelow is empty * "For the dates from 99.99.99 to 99.99.99" if neither is empty procedure forthedatesstr lparameters; datelow,; && D: date range low or empty datehigh && D: date range high or empty do case case empty(datelow) and empty(datehigh) return "For all dates" case !empty(datelow) and empty(datehigh) return "For the dates from "+dtocy2(datelow)+" on" case empty(datelow) and !empty(datehigh) return "For the dates up to "+dtocy2(datehigh) otherwise && case !empty(datelow) and !empty(datehigh) return "For the dates from "+dtocy2(datelow)+" to "+dtocy2(datehigh) endcase endproc * forthedatesshortstr * Generate "For the dates" Short String * Last Modification: 2015-06-17 * * Generates strings depending on datelow and datehigh being empty or not: * "For all dates" if datelow and datehigh are both empty * "For 99.99.99 on" if only datehigh is empty * "For up to 99.99.99" if only datelow is empty * "For 99.99.99 to 99.99.99" if neither is empty * * The reason for the routine is that sometimes, reports are too narrow for * the longer forms generated by forthedatesstr(). procedure forthedatesshortstr lparameters; datelow,; && D: date range low or empty datehigh && D: date range high or empty do case case empty(datelow) and empty(datehigh) return "For all dates" case !empty(datelow) and empty(datehigh) return "For "+dtocy2(datelow)+" on" case empty(datelow) and !empty(datehigh) return "For up to "+dtocy2(datehigh) otherwise && case !empty(datelow) and !empty(datehigh) return "For "+dtocy2(datelow)+" to "+dtocy2(datehigh) endcase endproc * fortheperiodstr * Generate "For the period" String * Last Modification: 2015-06-17 * * Generates strings depending on datelow and datehigh being empty or not: * "For all time" if datelow and datehigh are both empty * "For the period 99.99 on" if only datehigh is empty * "For the period up to 99.99" if only datelow is empty * "For the period 99.99 to 99.99" * if neither is empty and they are not in the same month * "For the period 99.99" if neither is empty and they are in the same month procedure fortheperiodstr lparameters; datelow,; && D: date range low or empty datehigh && D: date range high or empty do case case empty(datelow) and empty(datehigh) return "For all time" case !empty(datelow) and empty(datehigh) return "For the period from "+dtocyymm(datelow)+" on" case empty(datelow) and !empty(datehigh) return "For the period up to "+dtocyymm(datehigh) case !empty(datelow) and !empty(datehigh) and; left(dtos(datelow),6)#left(dtos(datehigh),6) return; "For the period from "+dtocyymm(datelow)+" to "+dtocyymm(datehigh) otherwise && case !empty(datelow) and !empty(datehigh) and && left(dtos(datelow),6)=left(dtos(datehigh),6) return "For the period "+dtocyymm(datelow) endcase endproc * wodaterange * Generate Work Order Date Range * Last Modification: 2015-08-17 * * Magic Number (sort of): this code generates the dates in YYMMDD format * regardless of the set century and set date settings. It is isolated here * so it can be more easily adjusted if that is later needed. procedure wodaterange lparameters datelow, datehigh return uctdatestr(datelow)+"-"+uctdatestr(datehigh) endproc * datercond * Create Date Range Conditional Expression * Last Modification: 2012-12-28 procedure datercond lparameters; fromfield,; && C: fieldname for from datefrom,; && D: date value for from tofield,; && C: fieldname for to dateto && D: date value for to local valuefrom, valueto, expr valuefrom=!isnull(datefrom) and !empty(datefrom) valueto=!isnull(dateto) and !empty(dateto) expr="" do case case !valuefrom and !valueto expr=".t." case valuefrom and !valueto expr=fromfield+">={^"+dtocy4(datefrom)+"}" case !valuefrom and valueto expr=tofield+"<={^"+dtocy4(dateto)+"}" otherwise && valuefrom and valueto expr=; fromfield+">={^"+dtocy4(datefrom)+"}"+; " and "+; tofield+"<={^"+dtocy4(dateto)+"}" endcase return expr endproc * dtroverlap * Date Range Overlap? * Last Modification: 2005-08-17 * * Check if the date range of datelow1 to datehigh1 overlaps any part of the * date range datelow2 to datehigh2. .t.=overlap, .f.=no overlap * * This is one of those picky little routines that can be miscoded all * too easily. procedure dtroverlap lparameters datelow1, datehigh1, datelow2, datehigh2 return !(datehigh2<datelow1 or datelow2>datehigh1) endproc ***** End of Included Code ***** Sincerely, Gene Wirchenko

6 9

Re: Fun with date calculations in VFP
by Gene Wirchenko 31 May '18

31 May '18

At 12:37 2018-05-21, Vince Teachout <teachv(a)taconic.net> wrote: >On 05/20/18 3:31 PM, Ted Roche wrote: >>On Sun, May 20, 2018 at 1:39 PM, Gene Wirchenko <genew(a)telus.net> wrote: >> >>> thedate=date(9999,12,31) && Handle this extreme case. >>And that, kids, is why we call it "The Y10K crisis..." > >I looking forward to all the $$$$ I'm going to make when people call >me in from retirement to fix all their old VFP programs before >midnight 9999! Can we say "Gouging rates?" "Gouging rates!" Yup! Now, you say it. >nb: Don't lose vfp install disk before then! Is there any version of VFP that handles dates after 9999? There was an early -- the first? -- version of dBASE III Plus that handled dates with years up to 32767. Sincerely, Gene Wirchenko

1 0

COM object in debugger Watch window
by Paul Newton 30 May '18

30 May '18

Hi all I have a COM object and when editing code intellisense shows me the objects properties and methods but when I am debugging I cannot see the objects properties in the watch window. Is there a way around this - perhaps something else I need to do in my C# code? Thanks Paul Newton

2 3

Windows 10 April 2018 Update & Running EXE from Shared drive (Samba)
by Mike 30 May '18

30 May '18

Heads up... After updating to Win 10 Pro 17134 (last night) apps that are stored on a network share (Samba server) will no longer run. Move the EXE file to a local drive and it works fine. Have already disabled firewall, no effect. Have moved all resource (DLL and FLL, OCX, APP) files to a local folder, no help. Move EXE file to a local folder, runs fine. Same application has run for years as a share, even over a VPN link. Mike Copeland

9 21

[NF] Let the meetings BEGIN.
by Stephen Russell 29 May '18

29 May '18

Our ERP vendor wants us to jump into the cloud in a multi-tenant data environment. Sucks for us having written many applications that read that data and present it to users to get things done that the ERP doesn't do today. Apply monthly price updates on items due to what the contract has for that customer. We then write those updates back to the ERP as well as send out a notification letter to every customer about price updates. When your data is in THIS cloud you give up the right to query it. Do they give access to APIs to pull what we need? Well they will think about that is what I thought I just heard. Happy Happy Joy Joy it looks like the next 2 quarters are going to be learning how to waste time on phone calls. -- Stephen Russell Sr. Analyst Ring Container Technology Oakland TN 901.246-0159 cell --- StripMime Report -- processed MIME parts --- multipart/alternative text/plain (text body -- kept) text/html ---

10 21

[NF] A Question of CPU Upgrade...
by Kurt at VR-FX 29 May '18

29 May '18

Hey there folks, Hope everyone is having a nice Memorial Day Weekend - at least those of us here that are States side! So - my main desktop PC was a Barebones system from Boxx Tech. that I built circa 2013. I haven't done any HW updates to it since I bought it. And, I just got am email from MicroCenter - with some nice deals. The one deal I am looking at - saves like $200 on an Intel CPU. But, I am wondering if its worth it to do the upgrade. Currently - the CPU is an Intel i7-4770 @ 3.4GHz - AFAIK its Quad Core. But, keep in mind - the current system has liquid cooling for the chip. And, although the machine was "barebones" - the chip and cooling system was already pre-installed. I simply installed HD, memory, SD HD, and a hi-end video card. Of course, since current system has an Intel chip - I need to stick w/Intel - even though I would love to go back to an AMD type chip - obviously I can't - and still keep same MoBo. As such - here is the chip on sale at MC: Coffee Lake Core i7-8700K 3.7GHz (Turbo Speed 4.7GHz) Six-Core/12 Processing Threads. So - would it be worth it to upgrade to this new chip? And, is it legit to swap a new chip like this into my system? I suspect its fully compatible. And, the other issue - not sure of the complications of the liquid cooling - and whether the chips can be swapped easily and still using same liquid cooling. Again - I haven't touched any HW stuff in this machine since it was built - which means I really haven't touch HW stuff for years. Although - I did swap an HD on this machine - since the primary HD died. TIA - L8r! -K-

4 11

2026

2025

2024

2023

2022

2021

2020

2019

2018

2017

2016

ProFox May 2018