By using this site, you agree to our updated Privacy Policy and our Terms of Use. Manage your Cookies Settings.
424,972 Members | 1,115 Online
Bytes IT Community
+ Ask a Question
Need help? Post your question and get tips & solutions from a community of 424,972 IT Pros & Developers. It's quick & easy.

Can Not Open Database

P: n/a
I have a database that raises an error when you try to open it and it
doesn't open. Trying to open the database with the OpenDatabase method
raises the same error. Trying to import any objects (tables, queies, forms,
etc) from the database raises the same error. Trying to link to the tables
in the database raises the same error. I am guessing there is an autoexec
macro or code in the open event of the opening form that contains the error.
Holding down the shift key does not seem to bypass the startup settings.

1. Is there any way from an external database to look at the properties of
the problem database to see if the AllowBypassKey is disabled?

2. Is there a way from command line parameters or an external database to
reset AllowBypassKey if it is disabled?

3. Any ideas on how to break into the problem database?

Thanks!

Steve
Mar 15 '07 #1
Share this Question
Share on Google+
12 Replies


P: n/a
On Thu, 15 Mar 2007 02:02:28 GMT, "Steve" <so***@private.emailaddress>
wrote:

Just curious: what would it take for you to divulge the exact error
message? Rather have us guess at it?

-Tom.
>I have a database that raises an error when you try to open it and it
doesn't open. Trying to open the database with the OpenDatabase method
raises the same error. Trying to import any objects (tables, queies, forms,
etc) from the database raises the same error. Trying to link to the tables
in the database raises the same error. I am guessing there is an autoexec
macro or code in the open event of the opening form that contains the error.
Holding down the shift key does not seem to bypass the startup settings.

1. Is there any way from an external database to look at the properties of
the problem database to see if the AllowBypassKey is disabled?

2. Is there a way from command line parameters or an external database to
reset AllowBypassKey if it is disabled?

3. Any ideas on how to break into the problem database?

Thanks!

Steve
Mar 15 '07 #2

P: n/a
No Problem!

Error# 3197

"The Microsoft Jet database engine stopped the process because you and
another user are attempting to change the same data at the same time."

Note: the database is a single user application.

Thanks!


"Tom van Stiphout" <no*************@cox.netwrote in message
news:eb********************************@4ax.com...
On Thu, 15 Mar 2007 02:02:28 GMT, "Steve" <so***@private.emailaddress>
wrote:

Just curious: what would it take for you to divulge the exact error
message? Rather have us guess at it?

-Tom.
>>I have a database that raises an error when you try to open it and it
doesn't open. Trying to open the database with the OpenDatabase method
raises the same error. Trying to import any objects (tables, queies,
forms,
etc) from the database raises the same error. Trying to link to the tables
in the database raises the same error. I am guessing there is an autoexec
macro or code in the open event of the opening form that contains the
error.
Holding down the shift key does not seem to bypass the startup settings.

1. Is there any way from an external database to look at the properties
of
the problem database to see if the AllowBypassKey is disabled?

2. Is there a way from command line parameters or an external database to
reset AllowBypassKey if it is disabled?

3. Any ideas on how to break into the problem database?

Thanks!

Steve

Mar 15 '07 #3

P: n/a
No Problem!

Error# 3197

"The Microsoft Jet database engine stopped the process because you and
another user are attempting to change the same data at the same time."

Note: the database is a single user application.

Thanks!


"Tom van Stiphout" <no*************@cox.netwrote in message
news:eb********************************@4ax.com...
On Thu, 15 Mar 2007 02:02:28 GMT, "Steve" <so***@private.emailaddress>
wrote:

Just curious: what would it take for you to divulge the exact error
message? Rather have us guess at it?

-Tom.
>>I have a database that raises an error when you try to open it and it
doesn't open. Trying to open the database with the OpenDatabase method
raises the same error. Trying to import any objects (tables, queies,
forms,
etc) from the database raises the same error. Trying to link to the tables
in the database raises the same error. I am guessing there is an autoexec
macro or code in the open event of the opening form that contains the
error.
Holding down the shift key does not seem to bypass the startup settings.

1. Is there any way from an external database to look at the properties
of
the problem database to see if the AllowBypassKey is disabled?

2. Is there a way from command line parameters or an external database to
reset AllowBypassKey if it is disabled?

3. Any ideas on how to break into the problem database?

Thanks!

Steve


Mar 15 '07 #4

P: n/a
On Mar 15, 1:25 pm, "Steve" <s...@private.emailaddresswrote:
No Problem!

Error# 3197

"The Microsoft Jet database engine stopped the process because you and
another user are attempting to change the same data at the same time."

Note: the database is a single user application.

Thanks!
See if there's an LDB file in the same directory. If there is, delete
it and then try to open the file.
Mar 15 '07 #5

P: n/a
Thanks for responding!

I have not been able to open the database since I received it so no LDB file
has ever been created.(I cheched - there is no LDB file.)

Steve
"ManningFan" <ma********@gmail.comwrote in message
news:11**********************@b75g2000hsg.googlegr oups.com...
On Mar 15, 1:25 pm, "Steve" <s...@private.emailaddresswrote:
>No Problem!

Error# 3197

"The Microsoft Jet database engine stopped the process because you and
another user are attempting to change the same data at the same time."

Note: the database is a single user application.

Thanks!

See if there's an LDB file in the same directory. If there is, delete
it and then try to open the file.


Mar 16 '07 #6

P: n/a
On Thu, 15 Mar 2007 17:25:20 GMT, "Steve" <so***@private.emailaddress>
wrote:

This can happen when you have two forms open, both in edit mode on the
same table. Going into edit mode could be caused by (typically bad)
code, rather than the user.

-Tom.

>No Problem!

Error# 3197

"The Microsoft Jet database engine stopped the process because you and
another user are attempting to change the same data at the same time."

Note: the database is a single user application.

Thanks!


"Tom van Stiphout" <no*************@cox.netwrote in message
news:eb********************************@4ax.com.. .
>On Thu, 15 Mar 2007 02:02:28 GMT, "Steve" <so***@private.emailaddress>
wrote:

Just curious: what would it take for you to divulge the exact error
message? Rather have us guess at it?

-Tom.
>>>I have a database that raises an error when you try to open it and it
doesn't open. Trying to open the database with the OpenDatabase method
raises the same error. Trying to import any objects (tables, queies,
forms,
etc) from the database raises the same error. Trying to link to the tables
in the database raises the same error. I am guessing there is an autoexec
macro or code in the open event of the opening form that contains the
error.
Holding down the shift key does not seem to bypass the startup settings.

1. Is there any way from an external database to look at the properties
of
the problem database to see if the AllowBypassKey is disabled?

2. Is there a way from command line parameters or an external database to
reset AllowBypassKey if it is disabled?

3. Any ideas on how to break into the problem database?

Thanks!

Steve
Mar 16 '07 #7

P: n/a
That's what I originally said I thought the problem is. I am guessing there
is an autoexec
macro or code in the open event of the opening form that contains the error.
Holding down the shift key does not seem to bypass the startup settings.

1. Is there any way from an external database to look at the properties of
the problem database to see if the AllowBypassKey is disabled?

2. Is there a way from command line parameters or an external database to
reset AllowBypassKey if it is disabled?

3. Any ideas on how to break into the problem database?

Thanks!

Steve

"Tom van Stiphout" <no*************@cox.netwrote in message
news:nu********************************@4ax.com...
On Thu, 15 Mar 2007 17:25:20 GMT, "Steve" <so***@private.emailaddress>
wrote:

This can happen when you have two forms open, both in edit mode on the
same table. Going into edit mode could be caused by (typically bad)
code, rather than the user.

-Tom.

>>No Problem!

Error# 3197

"The Microsoft Jet database engine stopped the process because you and
another user are attempting to change the same data at the same time."

Note: the database is a single user application.

Thanks!


"Tom van Stiphout" <no*************@cox.netwrote in message
news:eb********************************@4ax.com. ..
>>On Thu, 15 Mar 2007 02:02:28 GMT, "Steve" <so***@private.emailaddress>
wrote:

Just curious: what would it take for you to divulge the exact error
message? Rather have us guess at it?

-Tom.

I have a database that raises an error when you try to open it and it
doesn't open. Trying to open the database with the OpenDatabase method
raises the same error. Trying to import any objects (tables, queies,
forms,
etc) from the database raises the same error. Trying to link to the
tables
in the database raises the same error. I am guessing there is an
autoexec
macro or code in the open event of the opening form that contains the
error.
Holding down the shift key does not seem to bypass the startup settings.

1. Is there any way from an external database to look at the properties
of
the problem database to see if the AllowBypassKey is disabled?

2. Is there a way from command line parameters or an external database
to
reset AllowBypassKey if it is disabled?

3. Any ideas on how to break into the problem database?

Thanks!

Steve


Mar 16 '07 #8

P: n/a
On Fri, 16 Mar 2007 13:10:54 GMT, "Steve" <so***@private.emailaddress>
wrote:

Oh, right, I had forgotten about that. I re-read your OP and it seems
to me you should not get this error when trying to link to the tables.
Therefore I think the db is corrupt, and it may be quicker to restore
a backup.
You might want to try /readonly as a command line switch.
There is no special MDW involved here, right?
You have the same problems on another PC?

-Tom.
>That's what I originally said I thought the problem is. I am guessing there
is an autoexec
macro or code in the open event of the opening form that contains the error.
Holding down the shift key does not seem to bypass the startup settings.

1. Is there any way from an external database to look at the properties of
the problem database to see if the AllowBypassKey is disabled?

2. Is there a way from command line parameters or an external database to
reset AllowBypassKey if it is disabled?

3. Any ideas on how to break into the problem database?

Thanks!

Steve

"Tom van Stiphout" <no*************@cox.netwrote in message
news:nu********************************@4ax.com.. .
>On Thu, 15 Mar 2007 17:25:20 GMT, "Steve" <so***@private.emailaddress>
wrote:

This can happen when you have two forms open, both in edit mode on the
same table. Going into edit mode could be caused by (typically bad)
code, rather than the user.

-Tom.

>>>No Problem!

Error# 3197

"The Microsoft Jet database engine stopped the process because you and
another user are attempting to change the same data at the same time."

Note: the database is a single user application.

Thanks!


"Tom van Stiphout" <no*************@cox.netwrote in message
news:eb********************************@4ax.com ...
On Thu, 15 Mar 2007 02:02:28 GMT, "Steve" <so***@private.emailaddress>
wrote:

Just curious: what would it take for you to divulge the exact error
message? Rather have us guess at it?

-Tom.

>I have a database that raises an error when you try to open it and it
>doesn't open. Trying to open the database with the OpenDatabase method
>raises the same error. Trying to import any objects (tables, queies,
>forms,
>etc) from the database raises the same error. Trying to link to the
>tables
>in the database raises the same error. I am guessing there is an
>autoexec
>macro or code in the open event of the opening form that contains the
>error.
>Holding down the shift key does not seem to bypass the startup settings.
>
>1. Is there any way from an external database to look at the properties
>of
>the problem database to see if the AllowBypassKey is disabled?
>
>2. Is there a way from command line parameters or an external database
>to
>reset AllowBypassKey if it is disabled?
>
>3. Any ideas on how to break into the problem database?
>
>Thanks!
>
>Steve
>

Mar 16 '07 #9

P: n/a
Regarding trying to link to the tables - anything that tries to open the
database raises the error.

There is no special MDW involved here!

Same problem on other PCs.

Do you know any way to look at the properties of the problem database from
an external database?

Steve

"Tom van Stiphout" <no*************@cox.netwrote in message
news:jq********************************@4ax.com...
On Fri, 16 Mar 2007 13:10:54 GMT, "Steve" <so***@private.emailaddress>
wrote:

Oh, right, I had forgotten about that. I re-read your OP and it seems
to me you should not get this error when trying to link to the tables.
Therefore I think the db is corrupt, and it may be quicker to restore
a backup.
You might want to try /readonly as a command line switch.
There is no special MDW involved here, right?
You have the same problems on another PC?

-Tom.
>>That's what I originally said I thought the problem is. I am guessing
there
is an autoexec
macro or code in the open event of the opening form that contains the
error.
Holding down the shift key does not seem to bypass the startup settings.

1. Is there any way from an external database to look at the properties
of
the problem database to see if the AllowBypassKey is disabled?

2. Is there a way from command line parameters or an external database to
reset AllowBypassKey if it is disabled?

3. Any ideas on how to break into the problem database?

Thanks!

Steve

"Tom van Stiphout" <no*************@cox.netwrote in message
news:nu********************************@4ax.com. ..
>>On Thu, 15 Mar 2007 17:25:20 GMT, "Steve" <so***@private.emailaddress>
wrote:

This can happen when you have two forms open, both in edit mode on the
same table. Going into edit mode could be caused by (typically bad)
code, rather than the user.

-Tom.
No Problem!

Error# 3197

"The Microsoft Jet database engine stopped the process because you and
another user are attempting to change the same data at the same time."

Note: the database is a single user application.

Thanks!


"Tom van Stiphout" <no*************@cox.netwrote in message
news:eb********************************@4ax.co m...
On Thu, 15 Mar 2007 02:02:28 GMT, "Steve" <so***@private.emailaddress>
wrote:
>
Just curious: what would it take for you to divulge the exact error
message? Rather have us guess at it?
>
-Tom.
>
>
>
>>I have a database that raises an error when you try to open it and it
>>doesn't open. Trying to open the database with the OpenDatabase method
>>raises the same error. Trying to import any objects (tables, queies,
>>forms,
>>etc) from the database raises the same error. Trying to link to the
>>tables
>>in the database raises the same error. I am guessing there is an
>>autoexec
>>macro or code in the open event of the opening form that contains the
>>error.
>>Holding down the shift key does not seem to bypass the startup
>>settings.
>>
>>1. Is there any way from an external database to look at the
>>properties
>>of
>>the problem database to see if the AllowBypassKey is disabled?
>>
>>2. Is there a way from command line parameters or an external
>>database
>>to
>>reset AllowBypassKey if it is disabled?
>>
>>3. Any ideas on how to break into the problem database?
>>
>>Thanks!
>>
>>Steve
>>
>


Mar 17 '07 #10

P: n/a
"Steve" <so***@private.emailaddresswrote in
news:WH******************@newsread1.news.pas.earth link.net:
Do you know any way to look at the properties of the problem database
from an external database?
Yes, but this is very unlikely to work in the case you have described. It
opens the database from an automated instance of Access, and you have
pointed out that your database will not open.

An example can be found at
http://www.ffdba.com/downloads/Reset...Properties.htm

If I were faced with this problem I would try:

a) a compact (TTBOMK a repair is implicit in this operation) of the
database from another Access Application;
b) a request for the source (of the database that will not open)
organization or person to provide me with a copy that will open;
c) making a zipped copy of the db available on the net (assuming it's not
huge) in hopes that someone who had some spare time and found the problem
interesting or challenging mught solve it;
d) building the database anew; 99.44% of all Access databases are just crap
(example nwind.mdb) so why worry about one that's trashed?;
e) paying an Access recovery service to repair the database; I expect Peter
Miller could solve the problem in a few seconds but I have not seen any
mention of him or his business for quite a long time and I do not know if
his recovery business is active.
Mar 17 '07 #11

P: n/a
Thanks for responding!

What is "TTBOMK"?

"lyle fairfield" <ly******@yahoo.cawrote in message
news:oh****************@read1.cgocable.net...
"Steve" <so***@private.emailaddresswrote in
news:WH******************@newsread1.news.pas.earth link.net:
>Do you know any way to look at the properties of the problem database
from an external database?

Yes, but this is very unlikely to work in the case you have described. It
opens the database from an automated instance of Access, and you have
pointed out that your database will not open.

An example can be found at
http://www.ffdba.com/downloads/Reset...Properties.htm

If I were faced with this problem I would try:

a) a compact (TTBOMK a repair is implicit in this operation) of the
database from another Access Application;
b) a request for the source (of the database that will not open)
organization or person to provide me with a copy that will open;
c) making a zipped copy of the db available on the net (assuming it's not
huge) in hopes that someone who had some spare time and found the problem
interesting or challenging mught solve it;
d) building the database anew; 99.44% of all Access databases are just
crap
(example nwind.mdb) so why worry about one that's trashed?;
e) paying an Access recovery service to repair the database; I expect
Peter
Miller could solve the problem in a few seconds but I have not seen any
mention of him or his business for quite a long time and I do not know if
his recovery business is active.

Mar 17 '07 #12

P: n/a
"Steve" <so***@private.emailaddresswrote in
news:iz********************@newsread2.news.pas.ear thlink.net:
What is "TTBOMK"?
TTBOMK = "to the best of my knowledge"

--
lyle fairfield
-
Ceterum censeo Redmond esse delendam.
-
Mar 17 '07 #13

This discussion thread is closed

Replies have been disabled for this discussion.