t: Monday, April 09, 2018 1:29 PM
> To: profoxt...@leafe.com
> Subject: RE: .tmp Is Read-Only
>
> fyi NOFILTER==READWRITE
>
> --
>
> rk
>
> -Original Message-
> From: ProfoxTech On Behalf Of Frank Cazabon
> Sent: Monday, April 09, 2018 1:36 PM
> To: pro
Either one should let you create as many indexes as you want. But Tracy will
correct me if I'm wrong... 😊
--
rk
-Original Message-
From: ProfoxTech On Behalf Of Paul H. Tarver
Sent: Monday, April 09, 2018 2:45 PM
To: profoxt...@leafe.com
Subject: RE: .tmp Is Read-Only
: .tmp Is Read-Only
fyi NOFILTER==READWRITE
--
rk
-Original Message-
From: ProfoxTech On Behalf Of Frank Cazabon
Sent: Monday, April 09, 2018 1:36 PM
To: profoxt...@leafe.com
Subject: Re: .tmp Is Read-Only
Paul,
this is probably due to VFP's optimisation. Always get in the habit of
, April 09, 2018 12:27 PM
To: profoxt...@leafe.com
Subject: Re: .tmp Is Read-Only
Just to complete a little more what I wrote:
For Development I use a directory structure like this
\root-app-dir => Directory from where I run the code and the EXE,
and when MAIN.PRG is
\con
12:40 PM
To: profoxt...@leafe.com
Subject: Re: .tmp Is Read-Only
You're SQL cursor has to be made with the READWRITE clause if you're going
to try to create more than one index on the resulting cursor.
Fred
On Mon, Apr 9, 2018 at 10:35 AM, Frank Cazabon
wrote:
> Paul,
>
> this is pro
Ah. I stand corrected, Tracy. I was going from memory on what the documentation
says and did not recall that distinction.
--
rk
-Original Message-
From: ProfoxTech On Behalf Of Tracy Pearson
Sent: Monday, April 09, 2018 2:34 PM
To: profoxt...@leafe.com
Subject: RE: .tmp Is Read-Only
NOFILTER does not allow editing of the query results READWRITE does.
-Original Message-
From: ProfoxTech [mailto:profoxtech-boun...@leafe.com] On Behalf Of Richard
Kaye
Sent: Monday, April 09, 2018 2:29 PM
To: profoxt...@leafe.com
Subject: RE: .tmp Is Read-Only
fyi NOFILTER==READWRITE
fyi NOFILTER==READWRITE
--
rk
-Original Message-
From: ProfoxTech On Behalf Of Frank Cazabon
Sent: Monday, April 09, 2018 1:36 PM
To: profoxt...@leafe.com
Subject: Re: .tmp Is Read-Only
Paul,
this is probably due to VFP's optimisation. Always get in the habit of
using NOFILT
You're SQL cursor has to be made with the READWRITE clause if you're going
to try to create more than one index on the resulting cursor.
Fred
On Mon, Apr 9, 2018 at 10:35 AM, Frank Cazabon
wrote:
> Paul,
>
> this is probably due to VFP's optimisation. Always get in the habit of
> using NOFILTER
Paul,
this is probably due to VFP's optimisation. Always get in the habit of
using NOFILTER as part of your SQL SELECT command.
Try it and see if it works in both scenarios for you.
Without the NOFILTER, VFP may optimise the query by just opening the
cursor again with a filter applied, this
Just to complete a little more what I wrote:
For Development I use a directory structure like this
\root-app-dir => Directory from where I run the code and the EXE,
and when MAIN.PRG is
\config => contains the config.fpw included on the EXE/APP
\classes
Hi Paul,
1. Occurred to me, and I think that *could* have something to do with
Windows Folder Virtualization
2. When Windows can't write to your CFG dirs, then automatically select the
TEMP
In my experience with this "strange" errors, I've fixed them creating a
subdirectory by user behind a publ
Further testing has revealed a couple of things, but I still don't
understand the why.
The error is generating when I attempt to index the results of a query made
against SQL query resultant cursor. So, here's the logic: First, I send a
SQL Pass-through query to the server and store the large num
13 matches
Mail list logo
