+1 - and a few of us have made detailed suggestions, which are in Ed's
Archives.
On 02-Feb-2017 10:45 PM, Bob Lee wrote:
This discussion brings back memories :)
Bob Lee
-----Original Message-----
From: ProfoxTech [mailto:[email protected]] On Behalf Of Dave
Crozier
Sent: Thursday, February 2, 2017 7:59 AM
To: [email protected]
Subject: RE: SQL Backend Question
Paul,
No problem you asking here and you will get many types of feedback. I
slightly digress from Kurt's diagnosis as I am sure many on here will. We
are and have been going through a transition from legacy VFP data containers
onto Microsoft SQL and although it is a big job we haven't had to resort to
C# or any of the other languages Python etc... VFP is still a great tool to
do the front end processing and visualisation layer in projects despite
maybe being past its prime and it certainly is as quick in being able to
generate front ends even with fancy newstyle looks if you incorporate all
the addons that have been developed over the years.
Personally I took time out to develop a set of classes that allow me to run
multiple SQL sessions in multiple forms at the same time and we have used
them extensively. It takes all the heavy lifting out of SQL data
manipulation and leaves you, the developer to concentrate on what VFP does
best!!
Mike from MBS has been using MySQL as a back end for years and now
everything we do is client server so ask away...
Dave
-----Original Message-----
From: ProFox [mailto:[email protected]] On Behalf Of Paul H. Tarver
Sent: 02 February 2017 14:54
To: [email protected]
Subject: SQL Backend Question
Ok, I've lurked here long enough. I've been subscribed to this list for
several months and I have thoroughly enjoyed the questions and answers that
have come through during that time. I'm even a little star-struck when I see
the names of Foxpro experts that I have depended upon for years to help
educate me to be a better Foxpro programmer. Thank you all for all you do in
this list group. Now it is time for me to ask what is probably going to
sound like a dumb question coming from someone who has been using Foxpro
since Foxlan but I figure I have nothing to lose here and everything to
gain.
For the past few years I have been honing my skills as a developer of data
interfaces and until recently, the few full-fledged data entry projects I've
build relied upon native Foxpro dbf files. However, my interface work has
been depending more and more upon using SQL pass-through language to issue
queries against various SQL backend systems and I have been pretty
successful at retrieving data from various systems and then re-formatting
that data for other uses.
For a while now, I've been contemplating building a data-entry and
maintenance system from the ground up that depends completely upon using a
SQL database (Firebird, MySQL, MS SQL, Postgres or something similar). My
problem is that I have all these data handling classes built into a couple
of simple toolbars that I can drop on form and provide the standard Add,
Delete, Undo, Save and Exit functionality as well as a vcr toolbar to skip
between records. These tools include all of the code necessary to detect
changes enable various buttons based on conditions, etc. stuff we are all
familiar with.
Now I'm trying to wrap my head around the whole concept of changing the way
I depend upon Foxpro to handle much of the behind the scenes table activity
and create a new user interface that conforms to the how SQL works while
maintaining as much of the familiar functionality I'm so happy with in
Foxpro.
Does anyone have any recommendations for where I should go to learn more
about the best practices for developing user interfaces that work
efficiently with SQL backends, and what do I need to know about how to
collect data and insert it into the sql tables, detect user changes to flag
for saving data. In some software they seemed to have ditched the Add,
Delete, Undo, Save, Exit concept to just save everytime there is keystroke.
And in other systems, they keep parts of that old style of user interaction.
Are there any libraries that can be purchased or downloaded to handle some
of the behind the scenes data manipulation for SQL that I can use to learn
how this stuff should work.
For something that seems to be easy, I'm having a hard time letting go of my
20+ years of doing things the Foxpro way to make the transition.
Any thoughts?
Paul H. Tarver
Tarver Program Consultants, Inc.
--- StripMime Report -- processed MIME parts --- multipart/alternative
text/plain (text body -- kept)
text/html
---
[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: http://leafe.com/archives/search/profox
This message:
http://leafe.com/archives/byMID/profox/[email protected]
** 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.
