Re: "tempfile" is too large
- From: "christophe" <nothingtosend@xxxxxxxxx>
- Date: Wed, 30 Jan 2008 09:58:57 +0100
That seems to do the trick.
I replace eval() with &
kind regards
christophe
"Jeroen van Kalken" <I@xxxxxxxxxxxxxx> schreef in bericht
news:3mesp39c9k07cbclumamqpvuoah9mdrj7q@xxxxxxxxxx
On Mon, 28 Jan 2008 20:20:00 +0100, "news.microsoft.com" <no> wrote:
Could very well be since you are joining 2 tables...
If I'm not mistaken the EVAL() will only be done once, therefore
making a complete outerjoin of the two tables.
In this case you should use a macro-expansion
hmmm,
Hardly to imagine one table has 800 records (+-30 fields) the other 300
records (4fields) ....
regards
christophe
"Villi Bernaroli" <a@xxxxxxxxx> schreef in bericht
news:O0U15HcYIHA.4808@xxxxxxxxxxxxxxxxxxxxxxx
Villi Bernaroli wrote:
I got this message when running a report.
File c:\docume~1\christ~2\locals~1\temp\00004nx50025.tmp is too
large. when running :
SELECT * FROM trl,trlservice WHERE EVALUATE(afdrukdepotfilter) INTO
CURSOR "afdruktrl" readwrite
anybody an idea ?
Maybe your cursor went over the 3GB limit in VFP?
Sorry, I meant the 2GB limit.
--
News Microsoft
.
- References:
- "tempfile" is too large
- From: christophe
- Re: "tempfile" is too large
- From: Villi Bernaroli
- Re: "tempfile" is too large
- From: Villi Bernaroli
- Re: "tempfile" is too large
- From: news.microsoft.com
- Re: "tempfile" is too large
- From: Jeroen van Kalken
- "tempfile" is too large
- Prev by Date: Re: SQL Equivalent for Ascending/Descending
- Next by Date: Re: PJX OBJECT field contains personal info and being included in compiled executable.
- Previous by thread: Re: "tempfile" is too large
- Next by thread: SQL Help
- Index(es):
Relevant Pages
|