mdb keeps crashing

[jerry.ranch]

I've a database that is about 11mb, 117,000 records, about 15 fields.
When I run simple queries on the table, the database crashes
I've never seen anything like this before, any ideas?

This can't be good....

jerry

[DeanL]

You try compact/repair as that sometimes does the trick. Does the
database give any errors when it crashes or does it just freeze/exit
without an explanation?

[jerry.ranch]

exits with no explanation

You try compact/repair as that sometimes does the trick. Does the
database give any errors when it crashes or does it just freeze/exit
without an explanation?

[jerry.ranch]

Interesting Dean
I did a repair/compact and this is the first time I've even seen
Access drop a new table on me ..... MSysCompactError.
Chock full of 66 records..each identifying an error "could not find
field 'Description'

The databse is kaput.
All the records in all the fields have ############# now

It was a new database I was developing from some imported data..not
much lost. I wonder what happened?

Jerry
On 17 Feb 2006 12:08:10 -0800, "DeanL" <de*************@yahoo.com>
wrote:

You try compact/repair as that sometimes does the trick. Does the
database give any errors when it crashes or does it just freeze/exit
without an explanation?

[David W. Fenton]

je*********@pioneer.com wrote in
news:p2********************************@4ax.com:

Interesting Dean
I did a repair/compact and this is the first time I've even seen
Access drop a new table on me ..... MSysCompactError.
Chock full of 66 records..each identifying an error "could not
find field 'Description'

The databse is kaput.
All the records in all the fields have ############# now

It was a new database I was developing from some imported
data..not much lost. I wonder what happened?

What version of Access? This sounds like a problem that was common
in Jet 4 previous to Jet 4.0 service pack 6.

In any event, the fact that it didn't occur to you to compact the
database yourself suggests to me that this is something you do quite
rarely. It oughtn't be. Compacting is something that should be done
frequently during development, especially when importing lots of
data.

--
David W. Fenton http://www.dfenton.com/
usenet at dfenton dot com http://www.dfenton.com/DFA/

[jerry.ranch]

Using Access 2003 (11.6355.6408) SP1

Actually I do compact frequently (2-3 times daily; maybe thats NOT
frequent)... its just that this never occured to me as an option since
the database was only hours old. I have learned.

Thanks
Jerry

I did a repair/compact and this is the first time I've even seen
Access drop a new table on me ..... MSysCompactError.
Chock full of 66 records..each identifying an error "could not
find field 'Description'

The databse is kaput.
All the records in all the fields have ############# now

It was a new database I was developing from some imported
data..not much lost. I wonder what happened?

What version of Access? This sounds like a problem that was common
in Jet 4 previous to Jet 4.0 service pack 6.

In any event, the fact that it didn't occur to you to compact the
database yourself suggests to me that this is something you do quite
rarely. It oughtn't be. Compacting is something that should be done
frequently during development, especially when importing lots of
data.

[David W. Fenton]

je*********@pioneer.com wrote in
news:ju********************************@4ax.com:

Actually I do compact frequently (2-3 times daily; maybe thats NOT
frequent)... its just that this never occured to me as an option
since the database was only hours old. I have learned.

A need for a compact is a function of what operations have been
performed on the database, not of how long it's been in existence.
If you're importing and massaging data, frequent compacts are an
excellent idea, just to keep the file from bloating, but also to
improve performance, since it rewrites the data pages and,
especially, the indexes.

--
David W. Fenton http://www.dfenton.com/
usenet at dfenton dot com http://www.dfenton.com/DFA/