<!DOCTYPE html PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN">
<html>
<head>
<meta content="text/html;charset=ISO-8859-1" http-equiv="Content-Type">
</head>
<body bgcolor="#ffffff" text="#000000">
Christopher Yerry wrote:
<blockquote cite="mid20060202184018.92350.qmail@web54703.mail.yahoo.com"
type="cite">
<pre wrap="">Quoting Boaz Bezborodko (Thu, 02 Feb 2006 09:14:24
-0500):
[...]
</pre>
<blockquote type="cite">
<pre wrap="">I came across a webpage Jeremy Anderson put up
</pre>
</blockquote>
<pre wrap=""><!---->regarding
</pre>
<blockquote type="cite">
<pre wrap="">filePro. It does seem that he has a thing against
</pre>
</blockquote>
<pre wrap=""><!---->filePro in
</pre>
<blockquote type="cite">
<pre wrap="">that he spends as much time as he does publishing
</pre>
</blockquote>
<pre wrap=""><!---->against it.
</pre>
<blockquote type="cite">
<pre wrap="">But it could be the frustration of having to go
</pre>
</blockquote>
<pre wrap=""><!---->throught the
</pre>
<blockquote type="cite">
<pre wrap="">process of redoing someone's filePro database that
</pre>
</blockquote>
<pre wrap=""><!---->gets his
</pre>
<blockquote type="cite">
<pre wrap="">dander up.
</pre>
</blockquote>
<pre wrap=""><!---->[...]
</pre>
<blockquote type="cite">
<pre wrap="">He also seems a bit paranoid. He has a page called
</pre>
</blockquote>
<pre wrap=""><!---->"attempted > vendor intimidation" and "fPTech
nastygram" because Sue Rubin > sent a letter to his
company stating, in its entirety:
</pre>
<blockquote type="cite">
<pre wrap=""> We received this link from one of our filePro
</pre>
</blockquote>
<pre wrap=""><!---->clients and > were concerned that perhaps your
organization was having a
</pre>
<blockquote type="cite">
<pre wrap=""> problem with your filePro application that we
</pre>
</blockquote>
<pre wrap=""><!---->were not
</pre>
<blockquote type="cite">
<pre wrap=""> aware of. We would appreciate if you could
</pre>
</blockquote>
<pre wrap=""><!---->please let us
</pre>
<blockquote type="cite">
<pre wrap=""> know if there is a problem. We believe that it
</pre>
</blockquote>
<pre wrap=""><!---->was sent by
</pre>
<blockquote type="cite">
<pre wrap=""> a member of your >staff.
[URL deleted]
[Company name deleted] is a valued filePro client
</pre>
</blockquote>
<pre wrap=""><!---->and we
</pre>
<blockquote type="cite">
<pre wrap="">would
appreciate the opportunity to resolve any issues
</pre>
</blockquote>
<pre wrap=""><!---->in a private
</pre>
<blockquote type="cite">
<pre wrap=""> forum.
Hmm... "You seem to be having a problem with filePro
</pre>
</blockquote>
<pre wrap=""><!---->that we >weren't aware of. Let's work to solve it."
Yes, very
</pre>
<blockquote type="cite">
<pre wrap="">intimidating and nasty indeed.
</pre>
</blockquote>
<pre wrap=""><!---->
</pre>
<blockquote type="cite">
<pre wrap="">--
KenBrody at BestWeb dot net spamtrap:
</pre>
</blockquote>
<pre wrap=""><!---->
Boaz / Ken
Well I for one was offended ! (sorry for the sarcasm)
I would like to know how anyone (If anyone) shares
development tasks in a team environment or do we all
just DO IT ALL Ourselves.
It is worth noting filePro is unlike anything else in
methodology which is both good and bad - but that is
what makes it filePro, so the learning curve is large
coming from the MS .NET and java environments. Must of
us learned this 20 years ago when filePro was "cutting
edge" so I do not expect great reviews from "seasoned"
programmers.
Christopher Yerry
Pres CM Software
__________________________________________________
Do You Yahoo!?
Tired of spam? Yahoo! Mail has the best spam protection around
<a class="moz-txt-link-freetext" href="http://mail.yahoo.com">http://mail.yahoo.com</a>
</pre>
</blockquote>
<br>
I fully understand that much can be done with filePro and I have done
much of it myself. <br>
<br>
For me this is not my main job. I handle the programming work in my
own company because we couldn't afford to contract with someone else
back when we needed it. Since I enjoy doing occasional programming and
had already dabbled with making small changes in the existing system I
simply learned more of it as I needed. But the author does have a point
that some things can be a lot easier and, I feel, (admittedly not
knowing anything about what is underneath) done without changing the
basic functionality or structure of filePro. The While-do structure
and the ability to pass parameters without passing or duplicating
variable names are two areas that would make filePro an easier
development environment. It would also make filePro look a lot more
"familiar" to new programmers which is what filePro will depend on if
it is to grow.<br>
<br>
Imagine if you could make filepro programming look like what it does in
structured environments like VB or Pascal. The functionality would
still be there, the old programs would still work exactly as the same
without changes, but nested While-Do's would allow for a much more
readable, designable, and debuggable development environment and one
familiar to programmers who are only now learning the ropes.<br>
<br>
Like I said, I don't depend on filePro for my livelihood so this isn't
as important to me as it might be to many of you. I'm not married
filePro even as I use it and I'm not using anything else. I just
thought I would let you know how it looks like from someone who is far
more "outside" the filePro community than in it, but who is not wedded
to anything else. (IOW, I don't have any axes to grind.)<br>
<br>
bozob<br>
</body>
</html>