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

Strange Error Message Follow-up

P: n/a
Hello, all -

A few days ago, I posted the following message -

Hello all, and thank you for your help in the recent past.

Got a new error message in the last few days.

While working with different sized tables, in datasheet view, I've
gotten this message -

"THIS ACTION WILL RESET THE CURRENT CODE IN BREAK MODE."

There's a "Yes/No" message box. The choices are -

"To halt the execution of the program so the Module window can be
closed, select 'Yes'."
"To leave the code in the current state, select No".

I get the message when I try to close the datasheet view, either to go
to the Design View or to close it altogether. Pressing "Yes" does
nothing. The message box stays open and won't close. Pressing "No" gets
rid of the message box, but trying again to close the table brings the
message box back.

The only way to close the table is with Ctrl-Alt-Delete, and then
closing MSACCESS.EXE. Reopening the database and the same table reproduces
the error.

Some of the tables in question are large (6000 records, 18 fields), some
are small (300 records, 6 fields). I don't have any other forms open, so I
don't know what code is being described.

Any thoughts out there? TIA

A reply suggested creating a new database and importing the tables from the
old to the new. I was in the process of copying and pasting a table called
"tblTitleInfo" from the old to the new database when I discovered that the
"new" database thinks that it already has a table by that name, even though
the title does not appear in the container. It told me that there was
already a table by that name and asked me to confirm my desire to replace
the existing copy. I clicked "Yes" and got the following error message -

"The database engine could not lock table 'tblTitleInfo' because it is
already in use by another person or process."

Clicking "Help" at that point brings up a blank window with "Microsoft
Access" in the title bar - no help system.

I continued to copy tables, queries, forms and reports until I was done. I
closed both the old and new databases, re-opened the new database and
discovered that the forms, queries and reports had been lost. I then tried
to re-create the relationships and got the error about not being able to
lock the table 'tblTitleInfo'.

I'm totally befuzzled, and I don't have enough experience to try to sort
this out on my own. I have checked the Knowledge Base and came up with a fix
for a situation where a certain version of the Vbe6 DLL (I think) was used.
I do not have that version, thus I didn't try it.

Any thoughts? TIA, again.
Steve E.
(20 years without a beer. Startin' to think I might blow that in the very
near future.)

Nov 12 '05 #1
Share this Question
Share on Google+
3 Replies


P: n/a
Serious Practitioner,
Sounds like Access crashed with locks on some of the objects. The message
you got typically occurs when some code is interrupted because a variable
name or some other important bit has had its definition changed and VBA
can't continue. Ask Access to do a compact & repair and see if that cleans
up the locks that were left in the file. There is a utility called jetcomp
on the TechNet download site that will sometimes compact & repair jet
databases that seem to be ireperably damaged. And . . . your problem is
yet another reason why frequent backups of critical data & code are crucial.

"Serious_Practitioner" <Se************************@att.net> wrote in message
news:aE*********************@bgtnsc05-news.ops.worldnet.att.net...
Hello, all -

A few days ago, I posted the following message -

Hello all, and thank you for your help in the recent past.

Got a new error message in the last few days.

While working with different sized tables, in datasheet view, I've
gotten this message -

"THIS ACTION WILL RESET THE CURRENT CODE IN BREAK MODE."

There's a "Yes/No" message box. The choices are -

"To halt the execution of the program so the Module window can be
closed, select 'Yes'."
"To leave the code in the current state, select No".

I get the message when I try to close the datasheet view, either to go
to the Design View or to close it altogether. Pressing "Yes" does
nothing. The message box stays open and won't close. Pressing "No" gets rid of the message box, but trying again to close the table brings the
message box back.

The only way to close the table is with Ctrl-Alt-Delete, and then
closing MSACCESS.EXE. Reopening the database and the same table reproduces the error.

Some of the tables in question are large (6000 records, 18 fields), some are small (300 records, 6 fields). I don't have any other forms open, so I
don't know what code is being described.

Any thoughts out there? TIA

A reply suggested creating a new database and importing the tables from the old to the new. I was in the process of copying and pasting a table called
"tblTitleInfo" from the old to the new database when I discovered that the
"new" database thinks that it already has a table by that name, even though the title does not appear in the container. It told me that there was
already a table by that name and asked me to confirm my desire to replace
the existing copy. I clicked "Yes" and got the following error message -

"The database engine could not lock table 'tblTitleInfo' because it is
already in use by another person or process."

Clicking "Help" at that point brings up a blank window with "Microsoft
Access" in the title bar - no help system.

I continued to copy tables, queries, forms and reports until I was done. I
closed both the old and new databases, re-opened the new database and
discovered that the forms, queries and reports had been lost. I then tried
to re-create the relationships and got the error about not being able to
lock the table 'tblTitleInfo'.

I'm totally befuzzled, and I don't have enough experience to try to sort
this out on my own. I have checked the Knowledge Base and came up with a fix for a situation where a certain version of the Vbe6 DLL (I think) was used. I do not have that version, thus I didn't try it.

Any thoughts? TIA, again.
Steve E.
(20 years without a beer. Startin' to think I might blow that in the very
near future.)


Nov 12 '05 #2

P: n/a
Alan -

Thank you for your reply. I'll try both of your suggestions a bit later
tonight, and let you know how they work out.

Steve E.

"Alan Webb" <kn*****@hotmail.com> wrote in message
news:xV*****************@news.uswest.net...
Serious Practitioner,
Sounds like Access crashed with locks on some of the objects. The message
you got typically occurs when some code is interrupted because a variable
name or some other important bit has had its definition changed and VBA
can't continue. Ask Access to do a compact & repair and see if that cleans up the locks that were left in the file. There is a utility called jetcomp on the TechNet download site that will sometimes compact & repair jet
databases that seem to be ireperably damaged. And . . . your problem is
yet another reason why frequent backups of critical data & code are crucial.
"Serious_Practitioner" <Se************************@att.net> wrote in message news:aE*********************@bgtnsc05-news.ops.worldnet.att.net...
Hello, all -

A few days ago, I posted the following message -

Hello all, and thank you for your help in the recent past.

Got a new error message in the last few days.

While working with different sized tables, in datasheet view, I've
gotten this message -

"THIS ACTION WILL RESET THE CURRENT CODE IN BREAK MODE."

There's a "Yes/No" message box. The choices are -

"To halt the execution of the program so the Module window can be
closed, select 'Yes'."
"To leave the code in the current state, select No".

I get the message when I try to close the datasheet view, either to go to the Design View or to close it altogether. Pressing "Yes" does
nothing. The message box stays open and won't close. Pressing "No"

gets
rid of the message box, but trying again to close the table brings the
message box back.

The only way to close the table is with Ctrl-Alt-Delete, and then
closing MSACCESS.EXE. Reopening the database and the same table

reproduces
the error.

Some of the tables in question are large (6000 records, 18 fields),

some
are small (300 records, 6 fields). I don't have any other forms open, so I don't know what code is being described.

Any thoughts out there? TIA

A reply suggested creating a new database and importing the tables from

the
old to the new. I was in the process of copying and pasting a table called "tblTitleInfo" from the old to the new database when I discovered that the "new" database thinks that it already has a table by that name, even

though
the title does not appear in the container. It told me that there was
already a table by that name and asked me to confirm my desire to replace the existing copy. I clicked "Yes" and got the following error message -

"The database engine could not lock table 'tblTitleInfo' because it is already in use by another person or process."

Clicking "Help" at that point brings up a blank window with "Microsoft
Access" in the title bar - no help system.

I continued to copy tables, queries, forms and reports until I was done. I closed both the old and new databases, re-opened the new database and
discovered that the forms, queries and reports had been lost. I then tried to re-create the relationships and got the error about not being able to
lock the table 'tblTitleInfo'.

I'm totally befuzzled, and I don't have enough experience to try to sort
this out on my own. I have checked the Knowledge Base and came up with a

fix
for a situation where a certain version of the Vbe6 DLL (I think) was

used.
I do not have that version, thus I didn't try it.

Any thoughts? TIA, again.
Steve E.
(20 years without a beer. Startin' to think I might blow that in the very near future.)



Nov 12 '05 #3

P: n/a
Good morning -

As you suggested, I got and used the right version of Jetcomp, and I also
tried to run compact and repair a couple of times. I think that the compact
and repair process doesn't fully complete - there's a little progress bar in
the lower left area of the status bar that gets about halfway done, and then
stalls. It doesn't keep me from closing the database, it just stops. So that
seems to be out. Similarly Jetcomp, which seemed to run OK but made no
changes.

So is my next step to rebuild this database by hand? If so, if I export the
content only of the tables, will that avoid moving the "frozen" locks into a
new DB? Evidently the backup I have is also afflicted with this same
problem - I must have made a copy before I realized what was going on.

Thanks again.
Steve E.


"Alan Webb" <kn*****@hotmail.com> wrote in message
news:xV*****************@news.uswest.net...
Serious Practitioner,
Sounds like Access crashed with locks on some of the objects. The message
you got typically occurs when some code is interrupted because a variable
name or some other important bit has had its definition changed and VBA
can't continue. Ask Access to do a compact & repair and see if that cleans up the locks that were left in the file. There is a utility called jetcomp on the TechNet download site that will sometimes compact & repair jet
databases that seem to be ireperably damaged. And . . . your problem is
yet another reason why frequent backups of critical data & code are crucial.
"Serious_Practitioner" <Se************************@att.net> wrote in message news:aE*********************@bgtnsc05-news.ops.worldnet.att.net...
Hello, all -

A few days ago, I posted the following message -

Hello all, and thank you for your help in the recent past.

Got a new error message in the last few days.

While working with different sized tables, in datasheet view, I've
gotten this message -

"THIS ACTION WILL RESET THE CURRENT CODE IN BREAK MODE."

There's a "Yes/No" message box. The choices are -

"To halt the execution of the program so the Module window can be
closed, select 'Yes'."
"To leave the code in the current state, select No".

I get the message when I try to close the datasheet view, either to go to the Design View or to close it altogether. Pressing "Yes" does
nothing. The message box stays open and won't close. Pressing "No"

gets
rid of the message box, but trying again to close the table brings the
message box back.

The only way to close the table is with Ctrl-Alt-Delete, and then
closing MSACCESS.EXE. Reopening the database and the same table

reproduces
the error.

Some of the tables in question are large (6000 records, 18 fields),

some
are small (300 records, 6 fields). I don't have any other forms open, so I don't know what code is being described.

Any thoughts out there? TIA

A reply suggested creating a new database and importing the tables from

the
old to the new. I was in the process of copying and pasting a table called "tblTitleInfo" from the old to the new database when I discovered that the "new" database thinks that it already has a table by that name, even

though
the title does not appear in the container. It told me that there was
already a table by that name and asked me to confirm my desire to replace the existing copy. I clicked "Yes" and got the following error message -

"The database engine could not lock table 'tblTitleInfo' because it is already in use by another person or process."

Clicking "Help" at that point brings up a blank window with "Microsoft
Access" in the title bar - no help system.

I continued to copy tables, queries, forms and reports until I was done. I closed both the old and new databases, re-opened the new database and
discovered that the forms, queries and reports had been lost. I then tried to re-create the relationships and got the error about not being able to
lock the table 'tblTitleInfo'.

I'm totally befuzzled, and I don't have enough experience to try to sort
this out on my own. I have checked the Knowledge Base and came up with a

fix
for a situation where a certain version of the Vbe6 DLL (I think) was

used.
I do not have that version, thus I didn't try it.

Any thoughts? TIA, again.
Steve E.
(20 years without a beer. Startin' to think I might blow that in the very near future.)



Nov 12 '05 #4

This discussion thread is closed

Replies have been disabled for this discussion.