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

Access - crash when moving to next record...

P: n/a
Hello,

I have a completely new system (windows xp prof.),
office xp 2002 with sp 3.

When I create a new and empty Accesss database,
create an empty table and then create a new form
using a wizard, Access 2002 crashes when I go to
the next record using the little black arrow at the
bottom of the form...
I get a "send error report to microsoft..." message but this
is of no help for me.

Why? What is the problem and how to fix it?

By the way: If I create a button on the form, access creates code like this:

Private Sub Befehl0_Click()
On Error GoTo Err_Befehl0_Click
DoCmd.GoToRecord , , acNext '==> set breakpoint hier, breakpoint is reached

Exit_Befehl0_Click:
Exit Sub

Err_Befehl0_Click:
'==> this code here is never reached!!!!!!!!!!!!!!!!!!!!!!!!
MsgBox Err.Description
Resume Exit_Befehl0_Click

End Sub
This code does never goto to the label "Err_Befehl0_Click",
which I checked by debugging it using a breakpoint.

So I can't catch this error!!!

After this the database is destroyed, I can not use it any more.

Even the following strategy does not work:

%PATH_TO_ACCESSEXE%\MSAccess.exe /decompile %PATH_TO_ACCESSMDB_FILE%\db1.mdb

The database is repaired, by the problem stays...

Thank you very much for your support.
Nov 12 '05 #1
Share this Question
Share on Google+
4 Replies


P: n/a
It sounds as if something is corrupted or there is a conflict somewhere.
Things to check:

1) Current Video Driver (yes, even if this is a new machine)

2) www.windowsupdate.com (install the available updates, there will be about
45 MB of updates for a new machine. You can skip the dotNet framework v1.1,
unless you have programs that use dotNet, and other "add-ins" such as Media
Player and Windows Journal Viewer for these testing purposes. You may want
to go back and get them later. If WinXP SP1 is NOT installed, install this
update FIRST.)

3) Run a memory check (www.memtest86.com or
http://oca.microsoft.com/en/windiag.asp)

4) Get the hard drive manufacturer's testing utility and test the hard
drive.

5) Uninstall and Reinstall Office. Run chkdsk in between and clean out your
temp folders (%temp% and %windir%\temp)

--
Wayne Morgan
Microsoft Access MVP
"hinrich" <h.******@printpool-honsel.de> wrote in message
news:75**************************@posting.google.c om...
Hello,

I have a completely new system (windows xp prof.),
office xp 2002 with sp 3.

When I create a new and empty Accesss database,
create an empty table and then create a new form
using a wizard, Access 2002 crashes when I go to
the next record using the little black arrow at the
bottom of the form...
I get a "send error report to microsoft..." message but this
is of no help for me.

Why? What is the problem and how to fix it?

By the way: If I create a button on the form, access creates code like this:
Private Sub Befehl0_Click()
On Error GoTo Err_Befehl0_Click
DoCmd.GoToRecord , , acNext '==> set breakpoint hier, breakpoint is reached
Exit_Befehl0_Click:
Exit Sub

Err_Befehl0_Click:
'==> this code here is never reached!!!!!!!!!!!!!!!!!!!!!!!!
MsgBox Err.Description
Resume Exit_Befehl0_Click

End Sub
This code does never goto to the label "Err_Befehl0_Click",
which I checked by debugging it using a breakpoint.

So I can't catch this error!!!

After this the database is destroyed, I can not use it any more.

Even the following strategy does not work:

%PATH_TO_ACCESSEXE%\MSAccess.exe /decompile %PATH_TO_ACCESSMDB_FILE%\db1.mdb
The database is repaired, by the problem stays...

Thank you very much for your support.

Nov 12 '05 #2

P: n/a
h.******@printpool-honsel.de (hinrich) wrote in message news:<75**************************@posting.google. com>...
Hello,

I have a completely new system (windows xp prof.),
office xp 2002 with sp 3.

When I create a new and empty Accesss database,
create an empty table and then create a new form
using a wizard, Access 2002 crashes when I go to
the next record using the little black arrow at the
bottom of the form...
I get a "send error report to microsoft..." message but this
is of no help for me.

Why? What is the problem and how to fix it?

By the way: If I create a button on the form, access creates code like this:

Private Sub Befehl0_Click()
On Error GoTo Err_Befehl0_Click
DoCmd.GoToRecord , , acNext '==> set breakpoint hier, breakpoint is reached

Exit_Befehl0_Click:
Exit Sub

Err_Befehl0_Click:
'==> this code here is never reached!!!!!!!!!!!!!!!!!!!!!!!!
MsgBox Err.Description
Resume Exit_Befehl0_Click

End Sub
This code does never goto to the label "Err_Befehl0_Click",
which I checked by debugging it using a breakpoint.

So I can't catch this error!!!

After this the database is destroyed, I can not use it any more.

Even the following strategy does not work:

%PATH_TO_ACCESSEXE%\MSAccess.exe /decompile %PATH_TO_ACCESSMDB_FILE%\db1.mdb

The database is repaired, by the problem stays...

Thank you very much for your support.



+++++++++

Thanks for the hints!
Unfortunately, it's not a problem of my system, rather it must be a
microsoft bug, since we tried it on a notebook and on another desktop
system, the problem stays.

If I create a table, a form for this table using a wizard and then
enter data, now on a different system (the access database was created
on the original pc),
we have the same crash!!!

I will continue doing my work with java, this seems to be a much
better aproach.
Nov 13 '05 #3

P: n/a
h.******@printpool-honsel.de (hinrich) wrote in message news:<75**************************@posting.google. com>...
Hello,

I have a completely new system (windows xp prof.),
office xp 2002 with sp 3.

When I create a new and empty Accesss database,
create an empty table and then create a new form
using a wizard, Access 2002 crashes when I go to
the next record using the little black arrow at the
bottom of the form...
I get a "send error report to microsoft..." message but this
is of no help for me.

Why? What is the problem and how to fix it?

By the way: If I create a button on the form, access creates code like this:

Private Sub Befehl0_Click()
On Error GoTo Err_Befehl0_Click
DoCmd.GoToRecord , , acNext '==> set breakpoint hier, breakpoint is reached

Exit_Befehl0_Click:
Exit Sub

Err_Befehl0_Click:
'==> this code here is never reached!!!!!!!!!!!!!!!!!!!!!!!!
MsgBox Err.Description
Resume Exit_Befehl0_Click

End Sub
This code does never goto to the label "Err_Befehl0_Click",
which I checked by debugging it using a breakpoint.

So I can't catch this error!!!

After this the database is destroyed, I can not use it any more.

Even the following strategy does not work:

%PATH_TO_ACCESSEXE%\MSAccess.exe /decompile %PATH_TO_ACCESSMDB_FILE%\db1.mdb

The database is repaired, by the problem stays...

Thank you very much for your support.



+++++++++

Thanks for the hints!
Unfortunately, it's not a problem of my system, rather it must be a
microsoft bug, since we tried it on a notebook and on another desktop
system, the problem stays.

If I create a table, a form for this table using a wizard and then
enter data, now on a different system (the access database was created
on the original pc),
we have the same crash!!!

I will continue doing my work with java, this seems to be a much
better aproach.
Nov 13 '05 #4

P: n/a
hello,

if I read the help it could be a syntax-error.
"DoCmd.GoToRecord , , acNext" could contain 1 comma too much.
probably if the objecttype-parameter misses it doesn't expect a name
for the objecttype, and instead expexts the record-constant as second
parameter.
"DoCmd.GoToRecord" without parameters should do the same because
acNext is default.
the fact that the error-routine is not reached is probably because
'docmd' calls back the access-runtime and doesn't return to VBA after
the error.
Using the VBA-recordset to manipulate the cursor (or a
clone-recordset) doesn't need to exit VBA-contol and is - i think - a
more robust method if applicable in the context. Al least it gives
better control on error-conditions.
I did not test your problem, but I think this could explain it.

marc

h.******@printpool-honsel.de (hinrich) wrote in message news:<75**************************@posting.google. com>...
h.******@printpool-honsel.de (hinrich) wrote in message news:<75**************************@posting.google. com>...
Hello,

I have a completely new system (windows xp prof.),
office xp 2002 with sp 3.

When I create a new and empty Accesss database,
create an empty table and then create a new form
using a wizard, Access 2002 crashes when I go to
the next record using the little black arrow at the
bottom of the form...
I get a "send error report to microsoft..." message but this
is of no help for me.

Why? What is the problem and how to fix it?

By the way: If I create a button on the form, access creates code like this:

Private Sub Befehl0_Click()
On Error GoTo Err_Befehl0_Click
DoCmd.GoToRecord , , acNext '==> set breakpoint hier, breakpoint is reached

Exit_Befehl0_Click:
Exit Sub

Err_Befehl0_Click:
'==> this code here is never reached!!!!!!!!!!!!!!!!!!!!!!!!
MsgBox Err.Description
Resume Exit_Befehl0_Click

End Sub
This code does never goto to the label "Err_Befehl0_Click",
which I checked by debugging it using a breakpoint.

So I can't catch this error!!!

After this the database is destroyed, I can not use it any more.

Even the following strategy does not work:

%PATH_TO_ACCESSEXE%\MSAccess.exe /decompile %PATH_TO_ACCESSMDB_FILE%\db1.mdb

The database is repaired, by the problem stays...

Thank you very much for your support.



+++++++++

Thanks for the hints!
Unfortunately, it's not a problem of my system, rather it must be a
microsoft bug, since we tried it on a notebook and on another desktop
system, the problem stays.

If I create a table, a form for this table using a wizard and then
enter data, now on a different system (the access database was created
on the original pc),
we have the same crash!!!

I will continue doing my work with java, this seems to be a much
better aproach.

Nov 13 '05 #5

This discussion thread is closed

Replies have been disabled for this discussion.