On 2018-03-29 23:00, Joe Yoder wrote:
I have an SQL select statement that includes a group by clause to order
the
output for reporting. It gets its data from a table that potentially
includes legitimate duplicate records.
SELECT account, date, memo, paid_amoun;
FROM QB;
GROUP BY
Joe,
Use the Order by Clause to set your ordering. Group by will, by design,
eliminate duplicates. GROUP BY is used for aggregate functions, such as
sum(), count() etc.
On 03/29/18 11:00 PM, Joe Yoder wrote:
I have an SQL select statement that includes a group by clause to order the
I have an SQL select statement that includes a group by clause to order the
output for reporting. It gets its data from a table that potentially
includes legitimate duplicate records.
SELECT account, date, memo, paid_amoun;
FROM QB;
GROUP BY account, date, memo, paid_amoun;
INTO
Understood and I plan on doing a full review of each field before I'm done,
but I am at a point in the development where the SQL queries are very stable
and I thought it might be a good time to look for simple tweaks I could make
to optimize the connection and be able do some direct comparisons of
The return of data speed is always a volume concept. If you select * and
there are 40-100 columns and you really only need 20 only ask for them
back. Your speed will improve for quantities > 1000 rows.
On Thu, Mar 29, 2018 at 4:13 PM, Paul H. Tarver wrote:
> I was just
I was just about to post a follow up note for the group because once I
started testing with changing the default PacketSize, I realized that it
wasn't changing no matter what I did.
In response to your comments regarding optimizing the queries, I think I
should clarify that what I'm interested
If you have multiple repetitive queries to run on same db, consider writing
them to a working table on that server's db and then running
exec ProccessMyBatch
Of course, you have to create the sproc of ProcessMyBatch there as well. I
have no idea what the return of the initial process is so this
You can also use SQLPrepare() on the Fox end if you're going to be
repeatedly executing the same query with different parameters.
If you need the front end (VFP) to keep doing things while waiting for
the backend, you can set the connection as asynchronous and use
SQLMoreResults() to pull the
I was trying to play with packet size recently and it appears that the current
versions of the SQL ODBC driver have deprecated this parameter. At least my
attempts to change were met with failure.
I think the best opportunity for optimization would be to create your queries
as stored
I'm working on a project which involves issuing multiple queries across
several SQL databases and servers. At this point, I'm polling about 30
databases and retrieving data from four tables from each database.
I really have no reason to complain as my procedure including retrieving the
data
On 2018-03-29 13:59, Paul Hill wrote:
VFP was dropped from Visual Studio years ago.
The Community Edition is pretty nice, you can even use it to write
commercial software.
There is a limit of 5 users and company turnover IIRC.
On 29 March 2018 at 14:41, Kurt at VR-FX
VFP was dropped from Visual Studio years ago.
The Community Edition is pretty nice, you can even use it to write
commercial software.
There is a limit of 5 users and company turnover IIRC.
On 29 March 2018 at 14:41, Kurt at VR-FX wrote:
> That's interesting! I didn't even
Tracy,
Turns out it was the VFP data in my folder:
C:\Users\Dave Crozier\AppData\Roaming\Microsoft\Visual FoxPro 9
That was causing the problem.
Simply deleting it removed the error so I needn't have uninstalled and
installed VFP at all.
As for Ted's suggestion which I tried first, I have no
Dave,
Do you have a "Microsoft VisualFoxpro" folder under this location?
%LocalAppData%\VirtualStore\Program Files (x86)\
Paste that in the address bar of the File Explorer.
You might find a corrupt foxuser.dbf/fpt in there which is causing the
problem.
HTH,
Tracy
-Original Message-
Nice one!
Hell - CL recently just killed off the Entire Personals/dating section.
So - now I can't even sell myself on there!
:-)
-K-
On 3/29/2018 9:13 AM, Ted Roche wrote:
I guess Craigslist doesn't count for "NOT FOR RESALE."
On Wed, Mar 28, 2018 at 12:01 PM, Kurt at VR-FX
That's interesting! I didn't even know about this "Visual Studio
Community Edition" of VFP. I knew all this other stuff was Free - but, I
guess I never thought about there being a free version of VFP. What's
more interesting is - since M$ killed VFP YEARS ago - that makes it even
more
I thought RESOURCE=ON equals foxuser table, not the various reg keys that store
options. Dump it out to a file using F2B per Fernando's suggestion if you want
to save any of that data and tehn try packing it or just starting with a clean
one.
--
rk
-Original Message-
From:
I guess Craigslist doesn't count for "NOT FOR RESALE."
On Wed, Mar 28, 2018 at 12:01 PM, Kurt at VR-FX wrote:
> I just came across this posting on CL. Its mainly for VB - and its and older
> version 6 - but, seems VFP is included. I just kinda got a kick out of it -
> since
On Thu, Mar 29, 2018 at 7:24 AM, Dave Crozier wrote:
> Ted,
> Have searched the registry for all possible "open Last Project" options and
> can't find any setting that may hold the list of mru's. Have even tried to
> find one uniquely named project that would only occur
Richard,
The plot thickens now in that if I set Resource=ON then the same problem
arises, with the old pre-loaded projects so it must be the resources that are
screwing things up. I can't for the life of me find where these resources are
held though, I have cleaned the registry of all VFP and
Seems more likely to me that the culprit was the resource file and not the
PJX's, but either way it's quite gratifying to know I helped you arrive at a
solution. Much like getting a pat on the head from Uncle Ted...
--
rk
-Original Message-
From: ProfoxTech
Richard -> SUCCESS,
Your suggestion sorted it after I restored back last night's folder:
"C:\Program Files (x86)\Microsoft Visual FoxPro 9" in its entirety.
Setting the resource=off allowed me to load a barebones VFP and after loading
each of the projects that were causing VFP to hang I
On 3/29/2018 7:24 AM, Dave Crozier wrote:
Have searched the registry for all possible "open Last Project"
options and can't find any setting that may hold the list of mru's.
...
Somehow and somewhere VFP is picking up this last used list but I'll
be damned if I can find it. It may well be that
Dne 29.3.2018 v 13:24 Dave Crozier napsal(a):
Ted,
Have searched the registry for all possible "open Last Project" options and
can't find any setting that may hold the list of mru's. Have even tried to find one
uniquely named project that would only occur once in the registry if it was held
Hi Dave:
I have some ideas to check, based on similar situation in the past:
Preferences:
There are two things related to this; foxuser.dbf and the
"HKCU\Software\Microsoft\VisualFoxPro" registry key.
- Try deleting (or renaming) all foxuser.dbf you have, or convert to text
with FoxBin2Prg if
Have you tried loading VFP with a barebones config.fpw that includes
resource=off?
--
rk
-Original Message-
From: ProfoxTech On Behalf Of Dave Crozier
Sent: Thursday, March 29, 2018 6:36 AM
To: profoxt...@leafe.com
Subject: VFP9 Screwed - HELP!
Fellow
CONTACT
Got this one
On Wed, Mar 28, 2018 at 3:30 AM, Ken Dibble wrote:
> Not receiving my own posts?
--
.~. Might, Courage, Vision. SINCERITY!
/ v \ 64-bit Fedora 25 Server Spin
/( _ )\ http://sites.google.com/site/changmw
^ ^ May the Force and farces be with
With the freely available Visual Studio Community Edition, it'll be
hard to sell this one. :)
On Thu, Mar 29, 2018 at 12:01 AM, Kurt at VR-FX wrote:
> I just came across this posting on CL. Its mainly for VB - and its and older
> version 6 - but, seems VFP is included. I just
Ted,
Have searched the registry for all possible "open Last Project" options and
can't find any setting that may hold the list of mru's. Have even tried to find
one uniquely named project that would only occur once in the registry if it was
held there and can't find that either.
Somehow and
Tools/Options dialogs save its settings to the (evil, imho) Registry
so when you reinstall, you have all the wonderful features you
reinstalled to avoid.
Find "Open Last Project" option and turn it off. Shutdown VFP and restart.
If you can't start VFP because it's trying to open a bad project,
On 29/03/2018 11:35, Dave Crozier wrote:
Fellow Gurus.
Any input welcome as to why my VFP9 all serviced packed to date and working no
problem on Win 10, 64 bit has suddenly died and won't come back to life. Not
worried about why it went wrong, I just want a working VFP system.
For some reason
Fellow Gurus.
Any input welcome as to why my VFP9 all serviced packed to date and working no
problem on Win 10, 64 bit has suddenly died and won't come back to life. Not
worried about why it went wrong, I just want a working VFP system.
For some reason VFP remembers the old projects I had
32 matches
Mail list logo