Error Message

[Mike Labosh]

Access 2000 / Windows XP Pro SP2

Each of these tables lives by itself in its own mdb file (because they're
all pretty big), and I'm in a database where they are all linked. All the
files are on my local machine. When I ran this query, it churned the disk
for a few minutes and then threw an error message saying "Disk or network
error" and had a Help button that didn't do JACK. It's not using the
network, and my disk is fine, and I have a half gig of memory plus a gig of
swap space, so I know it's not having memory full issues either.

Can anyone offer some guesses as to what *actually happened*?

SELECT DISTINCT 'HardwareAAS' As FileType, Manufacturer, Prod_name,
Prod_type, Prod_series, Prod_model FROM HardwareAAS
UNION
SELECT DISTINCT 'HardwareMPDS1' As FileType, Manufacturer, Prod_name,
Prod_type, Prod_series, Prod_model FROM HardwareMPDS1
UNION
SELECT DISTINCT 'HardwareMPDS2' As FileType, Manufacturer, Prod_name,
Prod_type, Prod_series, Prod_model FROM HardwareMPDS2
UNION
SELECT DISTINCT 'HardwareMSM' As FileType, Manufacturer, Prod_name,
Prod_type, Prod_series, Prod_model FROM HardwareMSM
UNION
SELECT DISTINCT 'PrinterMSM' As FileType, Manufacturer, Prod_name,
Prod_type, Prod_series, Prod_model FROM PrinterMSM
UNION
SELECT DISTINCT 'StorageMSM' As FileType, Manufacturer, Prod_name,
Prod_type, Prod_series, Prod_model FROM StorageMSM
UNION
SELECT DISTINCT 'TapeMSM' As FileType, Manufacturer, Prod_name, Prod_type,
Prod_series, Prod_model FROM TapeMSM;

 

[Gijs Beukenoot]

Na rijp beraad schreef Mike Labosh :

Access 2000 / Windows XP Pro SP2

Each of these tables lives by itself in its own mdb file (because they're all
pretty big), and I'm in a database where they are all linked. All the files
are on my local machine. When I ran this query, it churned the disk for a
few minutes and then threw an error message saying "Disk or network error"
and had a Help button that didn't do JACK. It's not using the network, and
my disk is fine, and I have a half gig of memory plus a gig of swap space, so
I know it's not having memory full issues either.

Can anyone offer some guesses as to what *actually happened*?

SELECT DISTINCT 'HardwareAAS' As FileType, Manufacturer, Prod_name,
Prod_type, Prod_series, Prod_model FROM HardwareAAS
UNION
SELECT DISTINCT 'HardwareMPDS1' As FileType, Manufacturer, Prod_name,
Prod_type, Prod_series, Prod_model FROM HardwareMPDS1
UNION
SELECT DISTINCT 'HardwareMPDS2' As FileType, Manufacturer, Prod_name,
Prod_type, Prod_series, Prod_model FROM HardwareMPDS2
UNION
SELECT DISTINCT 'HardwareMSM' As FileType, Manufacturer, Prod_name,
Prod_type, Prod_series, Prod_model FROM HardwareMSM
UNION
SELECT DISTINCT 'PrinterMSM' As FileType, Manufacturer, Prod_name, Prod_type,
Prod_series, Prod_model FROM PrinterMSM
UNION
SELECT DISTINCT 'StorageMSM' As FileType, Manufacturer, Prod_name, Prod_type,
Prod_series, Prod_model FROM StorageMSM
UNION
SELECT DISTINCT 'TapeMSM' As FileType, Manufacturer, Prod_name, Prod_type,
Prod_series, Prod_model FROM TapeMSM;

Out of HD space?

I suggest cleaning your TEMP dir (usually \Documents and
Settings\<username>\Local Settings\Temp)

 

[Mike Labosh]

Out of HD space?

Nope. 13.9 gigs free

I suggest cleaning your TEMP dir (usually \Documents and
Settings\<username>\Local Settings\Temp)

Nope, I have an automated bot I wrote that dumps %TEMP% and %TMP% at bootup.

Anyone else want to take a stab at it?

 

[Steve Huff]

How big is each indivdual file? It's possible that Access can't handle the
size of bringing all 7 of them together at once or that one of them is
corrupt. Why don't you start out by running the query on two of them such
as:

SELECT DISTINCT 'HardwareAAS' As FileType, Manufacturer, Prod_name,
Prod_type, Prod_series, Prod_model FROM HardwareAAS
UNION
SELECT DISTINCT 'HardwareMPDS1' As FileType, Manufacturer, Prod_name,
Prod_type, Prod_series, Prod_model FROM HardwareMPDS1

and then keep adding one till you see the problem araise - skip the one with
the problem and see if you can add the others - if it's just one of them try
compacting and repairing it (or even muliples). That my at least help in
tracking down where the problem lies....

--Steve Huff

 

[Mike Labosh]

and then keep adding one till you see the problem araise - skip the one

with the problem and see if you can add the others - if it's just one of
them try compacting and repairing it (or even muliples). That my at least
help in tracking down where the problem lies....

Ahh, that's a cool idea. If one of the mdb's is corrupt, then this locates
it.

I just checked the actual file sizes. They're all over a gig, but the MPDS1
one is pretty close to the 2 gig limit. I bet that's my man.