Need help identifying an Error message my work computer keeps gett

[Guest]

My company has recently started using Mas90 with Microsoft Access 2003. We
keep getting the following error message whenever we leave Mas90 to go into
Access....

VBScript Error Number.... -2147467259
Description.............. [Microsoft][ODBC Microsoft Access Driver] Cannot
open database '(unknown)'. It may not be a database that your application
recognizes, or the file may be corrupt.
Line 58.............. (objconn.Open "DRIVER={Microsoft Access Driver
(*.mdb)};"&
strConnString
column............... 0

After the error occurs everybody has to get out of the Access program so
that the Admin. can compact & repair. After this has been done everybody can
get back into the program but in a matter of mins. to a couple of hrs. we
will get the message again. Can anyone tell me what is causing this and how
can we fix it. Thank You.

 

[Joseph Meehan]

My company has recently started using Mas90 with Microsoft Access
2003. We keep getting the following error message whenever we leave
Mas90 to go into Access....

VBScript Error Number.... -2147467259
Description.............. [Microsoft][ODBC Microsoft Access Driver]
Cannot open database '(unknown)'. It may not be a database that your
application recognizes, or the file may be corrupt.
Line 58.............. (objconn.Open "DRIVER={Microsoft Access Driver
(*.mdb)};"&
strConnString
column............... 0

After the error occurs everybody has to get out of the Access program
so that the Admin. can compact & repair. After this has been done
everybody can get back into the program but in a matter of mins. to a
couple of hrs. we will get the message again. Can anyone tell me
what is causing this and how can we fix it. Thank You.

That seems like a lot of errors to me. I suspect the network first.
What kind of network are you using.

In addition you may want to review the database design. First is it set
up as a split with a back end on the server and all users having their own
front end on their own machine? Are all the queries and static tables,
forms and reports needed by the users located on their machines or are they
on the server?

 

[Guest]

My company has recently started using Mas90 with Microsoft Access
2003. We keep getting the following error message whenever we leave
Mas90 to go into Access....

VBScript Error Number.... -2147467259
Description.............. [Microsoft][ODBC Microsoft Access Driver]
Cannot open database '(unknown)'. It may not be a database that your
application recognizes, or the file may be corrupt.
Line 58.............. (objconn.Open "DRIVER={Microsoft Access Driver
(*.mdb)};"&
strConnString
column............... 0

After the error occurs everybody has to get out of the Access program
so that the Admin. can compact & repair. After this has been done
everybody can get back into the program but in a matter of mins. to a
couple of hrs. we will get the message again. Can anyone tell me
what is causing this and how can we fix it. Thank You.

That seems like a lot of errors to me. I suspect the network first.
What kind of network are you using.

In addition you may want to review the database design. First is it set
up as a split with a back end on the server and all users having their own
front end on their own machine? Are all the queries and static tables,
forms and reports needed by the users located on their machines or are they
on the server?

Everything is on our server. We have tables/reports were more than one
person needs to work from at the same time.

 

[Joseph Meehan]

My company has recently started using Mas90 with Microsoft Access
2003. We keep getting the following error message whenever we leave
Mas90 to go into Access....

VBScript Error Number.... -2147467259
Description.............. [Microsoft][ODBC Microsoft Access Driver]
Cannot open database '(unknown)'. It may not be a database that
your application recognizes, or the file may be corrupt.
Line 58.............. (objconn.Open "DRIVER={Microsoft Access Driver
(*.mdb)};"&
strConnString
column............... 0

After the error occurs everybody has to get out of the Access
program so that the Admin. can compact & repair. After this has
been done everybody can get back into the program but in a matter
of mins. to a couple of hrs. we will get the message again. Can
anyone tell me what is causing this and how can we fix it. Thank
You.

That seems like a lot of errors to me. I suspect the network
first. What kind of network are you using.

In addition you may want to review the database design. First
is it set up as a split with a back end on the server and all users
having their own front end on their own machine? Are all the
queries and static tables, forms and reports needed by the users
located on their machines or are they on the server?

Everything is on our server. We have tables/reports were more than
one person needs to work from at the same time.

Access does not do well when everything is on the server. It works much
better in a multi user environment if each user has their own copy of a
front end and only the shared dynamic data is on the server.

In short the only thing that should be on the server is the data
(tables) that change. All the queries forms and reports as well as static
data, like maybe a city - state look up (cities seldom change states) should
also be on the front end (the part on each user's machine.

Access calls this a split database. details may be different in
different versions of Access but Access offers you a database
splitter-wizard to help you out. I suggest you look up split database in
the help files and read up a little. It should be well worth your while.

I suspect this will eliminate all or most of your errors. It will also
speed things up for the users. And it may provide improved functionality
for some users.

I would still suggest that you do a repair and compact of the back end
(the part on the server) on some sort of regular schedule, like once a week
or once a day.

You may even want to read up on user level security. If you decide to
try that however. please read the part about practicing on a copy of your
database and no risking the original.