ProFox July 2017

profox@leafe.com

49 participants
53 discussions

"Source not available" -- seems to happen in the history of the list!
by mbsoftwaresolutions＠mbsoftwaresolutions.com 28 Jul '17

28 Jul '17

VFP9SP2 Frustrated!!! All of the sudden my 2003 project code wants to rebel. I'm trying to debug some things and when I try to step into the code--code which has worked since 2003, mind you--it now says "Source not available" DESPITE THE FACT that I'm in the Project's home folder, where the EXE resides (I did a Build EXE & Run after), and the PROGS subfolder is in my path. Here's my first call to create the Custom biz obj: https://www.screencast.com/t/5UsbNGGXBGr Then here's the next screenshot, showing that nasty message and confirming my curdir() and SET('Path'): https://www.screencast.com/t/E1UOoe9h You can see in the first that I've even changed the pathing of the object call to what it really is. I never do that; I always used relative pathing like this: NEWOBJECT("Class",".\progs\_bizobj.prg") I searched the ProFox archives and saw this thread: https://leafe.com/archives/full_thread/468343 ...but Kurt's issue was resolved by relocating the EXE to the proper path. Mine is in the same spot it has been for 14 years! As Sytze (RIP) suggested, I deleted all of the FXP and did a COMPILE c:\dev\fabmate11\progs\*.prg to recreate all of them. Using Richard's tip, I verified that yes indeed, my project does have Debug Info included/checked in the Project manager. Also reviewed this thread, started by Richard: https://leafe.com/archives/full_thread/392144. I renamed the EXE and ran the new one....nope, same bad behavior. So I've ruled out pathing, out-of-sync FXPs, and the Hale-Bopp comet. I'm thinking my next step is to recreate the project file from scratch and rebuild. Any other ideas? tia, --Mike

6 13

3+month onsite VFP gig in West Mifflin, PA
by mbsoftwaresolutions＠mbsoftwaresolutions.com 28 Jul '17

28 Jul '17

From Ellen at EPS: Seeking VFP Contractor One of our clients is seeking a VFP Developer for an on-site only 3+ month contract in West Mifflin, PA. Development is for an existing custom ERP App written in VFP9 with DBF backend. If you are interested, please email your resume to info(a)codemag.com. Please only respond if you are available on-site. Have a great day! Ellen Whitney EPS Software & CODE Magazine I can't go onsite; otherwise I'd apply.

1 0

Re: "Source not available" -- seems to happen in the history of the list!
by Gene Wirchenko 28 Jul '17

28 Jul '17

At 10:10 2017-07-27, Ted Roche <tedroche(a)gmail.com> wrote: >On Thu, Jul 27, 2017 at 11:20 AM, ><mbsoftwaresolutions(a)mbsoftwaresolutions.com> wrote: > > VFP9SP2 > > > > Frustrated!!! All of the sudden my 2003 project code wants to rebel. > >Well, it is fourteen. Teenagers! My app is 20. Should I worry that it might want to start a family? Sincerely, Gene Wirchenko

2 1

RE: Variable/Procedure Naming Conventions
by Gene Wirchenko 28 Jul '17

28 Jul '17

At 00:29 2017-07-27, Paul Newton <Paul.Newton(a)pegasus.co.uk> wrote: > True. Why is the variable name not dDue? > >Because it could be an amount due? How so if the the prefix "d" means date? [snip] Sincerely, Gene Wirchenko

1 0

Determining VFP field to be AutoInc or not
by mbsoftwaresolutions＠mbsoftwaresolutions.com 27 Jul '17

27 Jul '17

VFP9SP2 I'm retrofitting old code and need to identify if the field's IID field in AutoInc or not. Looks like AFIELDS() is my friend here for array elements 17 and 18. Just wondered if anyone else had a better way? Thanks. --Mike

4 10

[NF] The 2017 Top Programming Languages: Python jumps to No. 1
by Malcolm Greene 27 Jul '17

27 Jul '17

The 2017 Top Programming Languages: Python jumps to No. 1 (article and reddit comments)http://spectrum.ieee.org/computing/software/the-2017-top-programmi… Malcolm --- StripMime Report -- processed MIME parts --- multipart/alternative text/plain (text body -- kept) text/html ---

2 1

Variable/Procedure Naming Conventions
by Paul H. Tarver 27 Jul '17

27 Jul '17

I was reading a chapter on 'Meaningful Names' in the book "Clean Code" by Robert C. Martin last night and right after he made a big point of using "Intention-Revealing Names" ie: make the name of a variable, procedure or function reflect its use, he then takes the opportunity to trash the Hungarian Notation system (and by extension I suppose any similar naming convention, including the YAlan Griver convention) saying that with today's strongly typed variables, notation like this is useless and should be avoided. Quite frankly, it hacked me off as I've spent the better part of 25 years learning and becoming disciplined enough to use the YAG naming convention as well as I could in FoxPro and I've used the same naming convention regardless of the language or its strongly typed variables because it works for me. In my world, any roadmap or breadcrumbs I can leave myself for future maintenance and standardization is a good thing. Thoughts? Paul H. Tarver Tarver Program Consultants, Inc. Email: <mailto:paul@tpcqpc.com> paul(a)tpcqpc.com --- StripMime Report -- processed MIME parts --- multipart/alternative text/plain (text body -- kept) text/html ---

8 13

Re: Variable/Procedure Naming Conventions
by Gene Wirchenko 27 Jul '17

27 Jul '17

At 10:51 2017-07-26, Stephen Russell <srussell705(a)gmail.com> wrote: >I have never been a fan of expressing the data-type in the name of the var >or function from VFP days on. lcCustomerName doesn't need c now does it? > dDueDate if you need to read a d as date, why is it in the blasted name? True. Why is the variable name not dDue? I sometimes code using prefixes. Mine are only related to type. For example, I use "c" for count, "x" for index, and "s" for size. All of these will probably be some integer type. >Everyone makes their own style and like art it is yours. And like art, it attracts critics. [snip] Sincerely, Gene Wirchenko

4 3

Re: Variable/Procedure Naming Conventions
by Gene Wirchenko 27 Jul '17

27 Jul '17

At 10:37 2017-07-26, "Paul H. Tarver" <paul(a)tpcqpc.com> wrote: >I was reading a chapter on 'Meaningful Names' in the book "Clean Code" by >Robert C. Martin last night and right after he made a big point of using >"Intention-Revealing Names" ie: make the name of a variable, procedure or >function reflect its use, he then takes the opportunity to trash the >Hungarian Notation system (and by extension I suppose any similar naming >convention, including the YAlan Griver convention) saying that with today's >strongly typed variables, notation like this is useless and should be >avoided. It seems to be tradition in some circles to trash Hungarian Notation. As I understand, Microsoft got its use wrong. This led to the crusade against HN. I use HN, but not for types in the programming language sense. I use it for specifying how a variable is intended to be used. An integer variable could be a count, an index, a size, or something else. I respectively use the prefixes "c", "x", and "s" for the first three. >Quite frankly, it hacked me off as I've spent the better part of 25 years >learning and becoming disciplined enough to use the YAG naming convention as >well as I could in FoxPro and I've used the same naming convention >regardless of the language or its strongly typed variables because it works >for me. Why invest the anger into this? >In my world, any roadmap or breadcrumbs I can leave myself for future >maintenance and standardization is a good thing. Exactly. >Thoughts? Carry on. You are doing fine. Sincerely, Gene Wirchenko

1 0

Array Declaration
by Laurie Alvey 24 Jul '17

24 Jul '17

I've always used DIMENSION a[] to declare an array but I've seen some developers use DECLARE a[]. Is there some subtle difference between te two statements? Laurie --- StripMime Report -- processed MIME parts --- multipart/alternative text/plain (text body -- kept) text/html ---

6 7

2026

2025

2024

2023

2022

2021

2020

2019

2018

2017

2016

ProFox July 2017