Database Problems After Compact and Repair

[Guest]

Hi guys,

We have a database split into the usual front and back end system (mdb). Our
database has started performing really slowly these last couple of weeks,
sometimes taking upto 2 minutes to run a simple query.

The back end mdb file is 59mb and I wondered if there was a problem with it
that might be fixed by a compact and repair. Running this process reduces the
filesize to 10mb, however after the process has completed, the front end no
longer functions properly with fields being whited out and error messages
occurring (examples of which I'll paste in a few minutes after I repeat this
processs again using our backup). Does anyone have any suggestions from the
limited information I have given?

The query which tends to grind the database to a halt is a very simple query
along the lines of SELECT * FROM tbl_phone_log WHERE entry_complete = FALSE
IT's really no more complicated than that and as far as I can see should in
no way grind the whole database to a halt or take 2/3 minutes to run.

Does anyone have any ideas or recommendations?

 

[Susie DBA [MSFT]]

yeah.. MDB isn't reliable enough for real world use

move to SQL Server and Acccess Data Projects

MDB has been obsolete for a decade.
DAO hasn't been included with Office, Windows or MDAC for a decade

I mean _DUH_

lose the training wheels, kid