Using filePro - Was Associated Fields and @AF

[Nancy Palmquist]

Christopher Yerry wrote:

 >  >> I'm going to guess you won't get too many nasty
 >  >> notes
 >  >> on this one. I agree that in most applications that
 >  >> child tables are the way to go. However, there are
 >  >> applications that are simple enough, where I
 > believe
 >  >> that associated fields are the way to go. As Jay
 >  >> mentioned, It eliminates the need for much code
 > that
 >  >> would otherwise be necessary. In simple
 >  >> applications,
 >  >> this can save you quite a bit of time.
 >
 >  > Every simple application you take a shortcut on will
 >  > be found by someone who will base a huge system on
 >  > it; (and then want you to fix it!)
 >  >  > cy
 >  >  >Shortcut vs. overkill.  As in most things it is not
 >  >black and white and requires a judgement call.  You
 >  >should not use an atom bomb to kill an ant hill.  I
 >  >think that you should use the amount of fire power
 >  >that is appropriate, and leave a reasonable amount of
 >  >room for growth.  Otherwise you are doing the customer
 >  >a dis-service.
 >  >
 >  >If it later turns out that you need to re-write all or
 >  >part of the application, then you hopefully will be
 >  >able to bill the client!
 >
 >  >Jeff Harrison
 >
 > Last comment and I will get off my soap box
 >
 > I will respectfully differ with that opinion
 >
 > I find it difficult to believe their are "file Pro" only shops 
around. I have converted many to .net but there are others that I don't 
want to mess with (their is too much code / not worth the change). If I 
take every table and make it relational (that's real relational not fp 
related fields relational) I can then use that data in any other 
environment. The related field mentality does not work anywhere else and 
if we want filePro to still exist it has to be able to be used accross 
the board - that's a relational table solution!
 >
 > So I believe I am saving my customers time and money by giving them 
this freedom. And the honest truth is most of the automatic processing 
is copied and modified slightly for each table so it doesn't take much 
time. Its just planning at the beginning. Most of my clients are 
impressed when we come to the table with this information. or with "you 
don't need to modify we already took that into consideration and its 
done".  /then they ask us to do something new!!/



Christopher,

I have to say that in my looks at "so called relational" databases, the 
records are connected with a unique identifier like a customer number, 
invoice number or the like.  I can easily find all detail that 
associates one to the other.  I think your issue is that it is not done 
for you.

I write filePro applications.  I have for over 20 years (as long as 
there has been filePro).  I do it for a living, full time.

I have designed many,many applications over the years and I have yet to 
see any other database that can offer the same flexibility, and ease of 
development.

Since I work for many companies, I have applications in many industries. 
  Solutions that give the customer the tools they need to manage the 
data.  I have seen issues with the way other applications manage data. I 
have seen the industry start with 8 bit data storage and grow to 64 bit 
stuff that boggles the mind.

I realize you are adapting to the changes in computing as you see but a 
solution is a solution.  I could step back and use the filepro product 
as a great front-end to any SQL server around. (Most anyway - not sure 
if ANY is too strong.)  I use it that way.  I can still develop a 
complex application in a fraction of the time required by any 
competitor.  I understand the GUI thing but for data entry and data 
management, GUI is awkward and slow, keyboard is better.

filePro has excellent tools for importing/exporting/integrating with 
other applications.  I am looking forward to the XML integration for 
reading and writing.  I already do this but maybe the tools will make it 
easier.

I have seen many companies try to duplicate a filePro application with 
another development language or try to replace a custom application with 
a canned program just to be very disappointed, much poorer, and often 
unsatified.  I have had my own customers fall for a sales presentation 
and empty promises and call me back when it all fell apart.

Now I don't say that filePro doesn't have its problems, but development 
speed is great, bugs are limited and the application is stable in most 
enviroments that I use.  Windows tends to be my most difficult 
environment, since it has issue with networking, client-side processing, 
  and I/O that tend to make any problem in those areas cause problems 
with the data.  I have many customers using Windows and only a few seem 
to be able to keep the basic computer system working so the database app 
can work correctly.

Now I have finished standing on my soapbox.  Sorry, but I think the 
customer is better served by building on what they have already invested 
instead of tearing it down and starting over.  My company grows and I 
add a wing to the building I don;t knock it all down and start over. 
Custom software is like that, you upgrade hardware, add new integration, 
add a wing but you don;t need to start over just because you can.

BTW - Associated fields are cool and no other data structure can do the 
same thing.  It can offer a lot of cool tricks.

Nancy

-- 
Nancy Palmquist         MOS & filePro Training Available
Virtual Software Systems    Web Based Training and Consulting
PHONE: (412) 835-9417           Web site:  http://www.vss3.com

-- 
Nancy Palmquist 		MOS & filePro Training Available
Virtual Software Systems	Web Based Training and Consulting	
PHONE: (412) 835-9417		   Web site:  http://www.vss3.com