Error opening an mdb file

[Laban Twissel]

Hi evrybody !

I 'm facing regularly the problem of my mdb database not opening, and
saying "an error ocuured qhile opening....do you want to repair ?..."
I must precise I'm still developping this database, so I'm still modifying
forms, queries and VBA code.

I've tried to design this db according to microsoft's advice (and to Allen
Brown's very usefull website) : the db is fully normalized, I close all my
objects, etc. However didn't I split the database into back/front end since
it has to stay a local database, and it would make much of my VBA code
harder (I use exclusively DAO to manipulate data).

What suprises me mostly is when close a working database one day (which I
have opened and close maybe ten times that day without the least problem)
and then got the error on trying to open it the day after, as if a ghost
had corrupted it during the night ! (but I don't believe in ghosts...)

Most of the time, I manage to open the mdb file by closing it (with or
without repairing) and trying again a few times. One time (in 2 month) have
I had to use JetComp. But I worry since I have to deliver the mdb file (not
an mde) and wouldn't like my client to encounter that problem.

Thanks for having read untill the end...and may the force be with you to
help me

Laban Twissel.

--

 

[Steve Huff]

Hi evrybody !

I 'm facing regularly the problem of my mdb database not opening, and
saying "an error ocuured qhile opening....do you want to repair ?..."
I must precise I'm still developping this database, so I'm still modifying
forms, queries and VBA code.

What version of Access are you using? Make sure you have all the patches
installed for your version of Access and Jet0

I've tried to design this db according to microsoft's advice (and to Allen
Brown's very usefull website) : the db is fully normalized, I close all my
objects, etc. However didn't I split the database into back/front end
since
it has to stay a local database, and it would make much of my VBA code
harder (I use exclusively DAO to manipulate data).

Splitting the database should not make your VBA code any harder - in fact it
should not have any effect on it at all unless you are doing SEEKS in which
case you would have to specificy the back end database when you open it
versus the currentDB. If you are not doing any SEEKS it shouldn't have any
effect on your code.

What suprises me mostly is when close a working database one day (which I
have opened and close maybe ten times that day without the least problem)
and then got the error on trying to open it the day after, as if a ghost
had corrupted it during the night ! (but I don't believe in ghosts...)

Are you developing on mulitple computers? I've seen problems where one
computer that didn't have the lastest patches on it corrupted the databases
only when it had opened and closed it.

Most of the time, I manage to open the mdb file by closing it (with or
without repairing) and trying again a few times. One time (in 2 month)
have
I had to use JetComp. But I worry since I have to deliver the mdb file
(not
an mde) and wouldn't like my client to encounter that problem.

Thanks for having read untill the end...and may the force be with you to
help me

Laban Twissel.

--

Try creating a brand new database and importing all your objects over to it.
If you have one particular object that is corrupt a lot of times that will
help narrow it down as it will bomb on that one object.

Hope some of this helps.

-Steve Huff

 

[Laban Twissel]

What version of Access are you using? Make sure you have all the
patches installed for your version of Access and Jet0
Are you developing on mulitple computers? I've seen problems where
one computer that didn't have the lastest patches on it corrupted the
databases only when it had opened and closed it.

Hi Steve and thanks for your help
I'm using access 2000 / Jet 4.0 with all patches (in my office) and access
2002 SP3 / Jet 4.0 at home. The file was created at office (2000) and I use
the least possible libraries to prevent problems...

Splitting the database should not make your VBA code any harder - in
fact it should not have any effect on it at all unless you are doing
SEEKS in which case you would have to specificy the back end database
when you open it versus the currentDB. If you are not doing any SEEKS
it shouldn't have any effect on your code.

What I meant is that Isplitting a database implies using a function to make
sure that the tables are attached, and I've read that some sql features
(agregate functions I think) are not available with attached tables

Try creating a brand new database and importing all your objects over
to it. If you have one particular object that is corrupt a lot of
times that will help narrow it down as it will bomb on that one
object.

Thanks I will try it.

Laban.