INDEX ON Transdate TAG Transdate
Do you get the same error with
INDEX ON DTOS(Transdate) TAG Transdate
Gérard.
___
Post Messages to: ProFox@leafe.com
Subscription Maintenance: http://leafe.com/mailman/listinfo/profox
OT-free version of this
I've seen some intermittent problems solved by putting a SELECT
csrTrans between the SELECT and the INDEX ON statement.
In addition to that, you could put an ORDER BY Transdate in the SELECT.
If they're using this table for viewing records, (and not SEEKing or
LOCATEing) then the result may be
Ken Dibble wrote:
I've checked the values in the Transdate column in that table: 1 record
with a crazy date back in the year 0120, 2 records where it was 0220, 1
from 1901 and the rest appear to be normal. And these goofy records
aren't even the ones in the query result.
I don't know the
Kevin Cully wrote:
I've seen some intermittent problems solved by putting a SELECT
csrTrans between the SELECT and the INDEX ON statement.
In addition to that, you could put an ORDER BY Transdate in the SELECT.
If they're using this table for viewing records, (and not SEEKing or
Gérard Lochon wrote:
INDEX ON Transdate TAG Transdate
Do you get the same error with
INDEX ON DTOS(Transdate) TAG Transdate
Hi Gérard,
It's a solution already deployed in the field, and I can't ship them an
updated EXE to test this. When I get their data, it doesn't fail for me
at all.
Michael Madigan wrote:
You're right, it should have nothing to do with locking on a local disk,
but know knows?
I would also turn off the local disk write caching to see if that makes
a difference.
Did that already...problem still crept up.
It could also be a phony error that's completely
Anti-Virus gets a lock.
-Original Message-
From: MB Software Solutions General Account
Sent: Tuesday, September 30, 2008 6:13 PM
We've got a client in the field who runs a report and it creates an oddball
error, one that no one else is apparently gettingand the best part---it
IT might also be opportunistic locking causing a problem. Just for laughs,
turn off opportunistic locking on that share.
--- On Tue, 9/30/08, Tracy Pearson [EMAIL PROTECTED] wrote:
From: Tracy Pearson [EMAIL PROTECTED]
Subject: RE: VFP9SP1 Error 1705 access denied when running INDEX
Michael Madigan wrote:
IT might also be opportunistic locking causing a problem. Just for
laughs, turn off opportunistic locking on that share.
It's totally LOCAL, not on the LAN, so that doesn't seem likely. Isn't
that suggestion for LAN files only?
.
--- On Tue, 9/30/08, MB Software Solutions General Account [EMAIL PROTECTED]
wrote:
From: MB Software Solutions General Account [EMAIL PROTECTED]
Subject: Re: VFP9SP1 Error 1705 access denied when running INDEX on
MyDateFld tag MyDateFld
To: ProFox Email List profox@leafe.com
Date
I've checked the values in the Transdate column in that table: 1 record
with a crazy date back in the year 0120, 2 records where it was 0220, 1
from 1901 and the rest appear to be normal. And these goofy records
aren't even the ones in the query result.
I don't know the answer to your problem
11 matches
Mail list logo
