Running Query Removes Linked Table Association?

[hafner]

Hello all,

I have an extremely simple query I'm running on a linked table.
However, when I run it (primarily, I'm exporting to a .txt file, but
the behavior persists even if I run the query), it returns zero
results. Then, when I view the table, it has zero records.

If I re-establish the link to the table, the table shows full of data
again. I run the query, it returns zero results, the table is empty
again.

Once, I ran the query and it returned ~10% of the results, and the
table had ~10% of its data remaining. As usual, when I re-established
the link to the table, it showed up with the normal data set.

Any ideas? As I say, it's an extremely simple query:
SELECT ProductData.ASIN
FROM ProductData
GROUP BY ProductData.ASIN;

The linked table is a .txt file in the same folder as the database; it
is too large to import into the database directly.

Cheers,
Chris Hafner

[Tom van Stiphout]

On Mon, 27 Aug 2007 13:27:47 -0700, ha****@peoplepc.com wrote:

This query is equivalent to:
select distinct ASIN from ProductData
See if it gives you better results.

How big is your text file? Perhaps you could import it in SQL Server.
I think the text ISAM is a bit limited.

-Tom.

>Hello all,

I have an extremely simple query I'm running on a linked table.
However, when I run it (primarily, I'm exporting to a .txt file, but
the behavior persists even if I run the query), it returns zero
results. Then, when I view the table, it has zero records.

If I re-establish the link to the table, the table shows full of data
again. I run the query, it returns zero results, the table is empty
again.

Once, I ran the query and it returned ~10% of the results, and the
table had ~10% of its data remaining. As usual, when I re-established
the link to the table, it showed up with the normal data set.

Any ideas? As I say, it's an extremely simple query:
SELECT ProductData.ASIN
FROM ProductData
GROUP BY ProductData.ASIN;

The linked table is a .txt file in the same folder as the database; it
is too large to import into the database directly.

Cheers,
Chris Hafner

[ARC]

Could you write code to process the text file, line by line, and write the
results into an access table? That would seem to be a better way to go than
linking to a text file. If you need code samples for processing a flat file,
let me know.

Andy