A2K Runtime Crashes on DoCmd.Quit

[Gina Whipp]

Andy,

I am stumped. I guess I would try uninstalling and reinstalling and/or
recreating the button. But after that I am not sure what to try next.

--
Gina Whipp

"I feel I have been denied critical, need to know, information!" - Tremors
II

Its the same Microsoft ActiveX Data Objects 2.8 Library being used on the
test computers that do run the app correctly as it is on the re-built
computer.
Same order. Same files. MDE / MDB. Same install CD.

Found a note that said originally it was Microsoft ActiveX Data Objects
2.1 Library.

Changed it back to 2.1 but it still gets Runtime Crash on the re-built
computer.

Andy

And they are the same for the machines that work and the one that doesn't
work and in the same order?

--
Gina Whipp

"I feel I have been denied critical, need to know, information!" -
Tremors II

Yes have Admin rights.

The references are correct. Meaning they are the same as when the
Runtime app was originally installed in 2007.
Visual Basic for Applications
Microsoft Access 9.0 Object Library
OLE Automation
Microsoft ActiveX Data Objects 2.8 Library
Microsoft DAO 3.6 Object Library
Microsoft Word 9.0 Object Library
Microsoft Visual Basic for Applications Extensibility 5.3

Andy

Is it possible for you to check the References on a machine it does run
on to the machine it doesn't run on? Do you have Admin rights to this
database?

--
Gina Whipp

"I feel I have been denied critical, need to know, information!" -
Tremors II
Gina;

Thank You.

All updates and patches in place for both Windows XP Pro & Office
including Access Runtime.

There is no network path.
We are trying to Re_Install on a stand alone computer using the same
install
CD that originally installed a RunTime version of Access 2000 (ART) and
ran
an app that was created using Office Developer 2000.

This particular computer had to be "Re-built". Windows and everything
else
was re-installed from scratch about 2 weeks ago.

Only One User. No network involved.
The BE is MDE the FE MDB & Secured.MDW with User Level Permissions.

The Splash Screen displays correctly and the Login frm allows the User
to
enter a password. So I know Access Runtime is installed correctly.

Its when the User clicks on either cmdLogin or cmdExit is when the
crash
occurs.

The frmLogin has 3 Controls:
txtPwordAsk (User enters the password)
UnBound.

cmdLogin
OnClick:
If Me![txtPwordAsk] = (DLookup("[MyPWord]", "tblMain")) Or
Me![txtPwordAsk] = "*SpecialPWord*" Then
DoCmd.OpenForm "frmMain"
DoCmd.Close acForm, "frmLogin"
Else
Msg = MsgBox("That is not the correct Password." & vbCrLf & _
"Please enter the Password once more.", vbOKOnly + vbInformation,
"OurCompany")
Me![txtPwordAsk] = Null
Me![txtPwordAsk] = Null ' Don't know why this line is here twice.
DoCmd.GoToControl "txtPwordAsk"
End If

cmdExit
OnClick:
DoCmd.Quit

This same code has been used on that re-built stand alone since 2007.

With this current re-install of Windows and all applications when the
User clicks on either cmdButton an Access Runtime Crash occurs.

With or Without PWord typed in when the User clicks on either cmdButton
an Access Runtime Crash occurs and Access shutsdown.

Have seen this same type of crash before when the permissions for a frm
were not granted to the User. Verified the User had Open/Run
permissions for frmLogin. Also gave it Read Design permission. Still
crashed in same places.

What is odd to me is that it is even getting a RunTime crash with:
cmdExit OnClick: DoCmd.Quit
DoCmd.Quit should if nothing else close the app without crashing.

Lady and Gentlemen is there anymore information You might need to help
You help me to overcome this obstacle?

Thank You for taking the time to read this post.

Andy


Andy,

Let's start with obvious... Are all the patches for Windows and Office
applied? Then check network paths to make sure they are set up the
same.
And why are installing a seperate BE, isn't everyone connected to the
same
BE?

--
Gina Whipp

"I feel I have been denied critical, need to know, information!" -
Tremors
II

Gina;

Thank You for reading and replying to my post.

What I mean is that I have installed the app on other computers to
test
the installation. All of those machines are stand alones as is the
computer that is getting the Runtime crash.

The computer that the app has been running on for years crashed out
and
Windows needed to be re-installed from scratch.
Now, using the same install CD and the Same FE (MDB) and BE (MDE) we
are
getting Runtime crashes no matter if we click on cmdContinue to open
another frm or to simply click Exit to shut the app down.

Andy


Andy,

Are you saying that when not on stand alone machines everyone is
accessing the same front end? I think more details are going to be
needed to figure out exactly what your issue is.

--
Gina Whipp

"I feel I have been denied critical, need to know, information!" -
Tremors II

Gentlemen;

Thank You all for reading and replying to my post.

Created this mdb front end and mde back using Office 2000
Developer.

Its not that Dbase doesn't run At All. It does run on other
machines,
(all
Stand Alones).

The Crash happens at the "Log In" frm.

No matter if the User clicks "Continue" or the cmdExit OnClick
Event is:
Private Sub cmdExit_Click()
DoCmd.Quit
End Sub

Access Crashes due to a RunTime Error.

Why? How do I discover what is crashing? What is causing it?

Again Thank You for taking the time to read and reply to my post.

Andy


"a a r o n . k e m p f @ g m a i l . c o m" <[email protected]>
wrote in message
Rob;

Maybe if you knew how to work the worlds most popular database,
then
maybe- just maybe- you wouldn't be stuck wiht a paperweight-sized
database






On Dec 29, 9:50 pm, Robert Morley
<[email protected]>
wrote:
Tony Toews [MVP] wrote:

Please ignore Aaron Kempf's posting as he responds with SQL
Server
and
ADPs as the answer even when that would have no resemblance to
the
problem.

Tony

What's funny about this is that in the case I spoke of, I was
using an
A2K
ADP.

Rob

 

[Gina Whipp]

Maybe you could copy/paste this and see if it works or at the very least we
get a REAL error message...

Private Sub cmdExit_Click()
On Error GoTo Err_ExitDatabase_Click

DoCmd.Quit

Exit_ExitDatabase_Click:
Exit Sub

Err_ExitDatabase_Click:
MsgBox Error$
Resume Exit_ExitDatabase_Click

End Sub

 

[Andy]

Gina;

Thank You for Your time.

Have tried un-install / re-install at least 3 times already on this
particular computer. Still No Go.

The question is simply: Why does "DoCmd.Quit" cause a Runtime Crash?

Going to wait a few more hours for anymore replies to this post then going
to Post again with the subject line being that question.
Why does "DoCmd.Quit" cause a Runtime Crash?

Again Thank All for reading and replying to this post.

Happy New Year.

Andy

Andy,

I am stumped. I guess I would try uninstalling and reinstalling and/or
recreating the button. But after that I am not sure what to try next.

--
Gina Whipp

"I feel I have been denied critical, need to know, information!" - Tremors
II

Its the same Microsoft ActiveX Data Objects 2.8 Library being used on the
test computers that do run the app correctly as it is on the re-built
computer.
Same order. Same files. MDE / MDB. Same install CD.

Found a note that said originally it was Microsoft ActiveX Data Objects
2.1 Library.

Changed it back to 2.1 but it still gets Runtime Crash on the re-built
computer.

Andy

And they are the same for the machines that work and the one that
doesn't work and in the same order?

--
Gina Whipp

"I feel I have been denied critical, need to know, information!" -
Tremors II

Yes have Admin rights.

The references are correct. Meaning they are the same as when the
Runtime app was originally installed in 2007.
Visual Basic for Applications
Microsoft Access 9.0 Object Library
OLE Automation
Microsoft ActiveX Data Objects 2.8 Library
Microsoft DAO 3.6 Object Library
Microsoft Word 9.0 Object Library
Microsoft Visual Basic for Applications Extensibility 5.3

Andy

Is it possible for you to check the References on a machine it does
run on to the machine it doesn't run on? Do you have Admin rights to
this database?

--
Gina Whipp

"I feel I have been denied critical, need to know, information!" -
Tremors II
Gina;

Thank You.

All updates and patches in place for both Windows XP Pro & Office
including Access Runtime.

There is no network path.
We are trying to Re_Install on a stand alone computer using the same
install
CD that originally installed a RunTime version of Access 2000 (ART)
and ran
an app that was created using Office Developer 2000.

This particular computer had to be "Re-built". Windows and everything
else
was re-installed from scratch about 2 weeks ago.

Only One User. No network involved.
The BE is MDE the FE MDB & Secured.MDW with User Level Permissions.

The Splash Screen displays correctly and the Login frm allows the User
to
enter a password. So I know Access Runtime is installed correctly.

Its when the User clicks on either cmdLogin or cmdExit is when the
crash
occurs.

The frmLogin has 3 Controls:
txtPwordAsk (User enters the password)
UnBound.

cmdLogin
OnClick:
If Me![txtPwordAsk] = (DLookup("[MyPWord]", "tblMain")) Or
Me![txtPwordAsk] = "*SpecialPWord*" Then
DoCmd.OpenForm "frmMain"
DoCmd.Close acForm, "frmLogin"
Else
Msg = MsgBox("That is not the correct Password." & vbCrLf & _
"Please enter the Password once more.", vbOKOnly + vbInformation,
"OurCompany")
Me![txtPwordAsk] = Null
Me![txtPwordAsk] = Null ' Don't know why this line is here twice.
DoCmd.GoToControl "txtPwordAsk"
End If

cmdExit
OnClick:
DoCmd.Quit

This same code has been used on that re-built stand alone since 2007.

With this current re-install of Windows and all applications when the
User clicks on either cmdButton an Access Runtime Crash occurs.

With or Without PWord typed in when the User clicks on either
cmdButton an Access Runtime Crash occurs and Access shutsdown.

Have seen this same type of crash before when the permissions for a
frm were not granted to the User. Verified the User had Open/Run
permissions for frmLogin. Also gave it Read Design permission. Still
crashed in same places.

What is odd to me is that it is even getting a RunTime crash with:
cmdExit OnClick: DoCmd.Quit
DoCmd.Quit should if nothing else close the app without crashing.

Lady and Gentlemen is there anymore information You might need to help
You help me to overcome this obstacle?

Thank You for taking the time to read this post.

Andy


Andy,

Let's start with obvious... Are all the patches for Windows and
Office
applied? Then check network paths to make sure they are set up the
same.
And why are installing a seperate BE, isn't everyone connected to the
same
BE?

--
Gina Whipp

"I feel I have been denied critical, need to know, information!" -
Tremors
II

Gina;

Thank You for reading and replying to my post.

What I mean is that I have installed the app on other computers to
test
the installation. All of those machines are stand alones as is the
computer that is getting the Runtime crash.

The computer that the app has been running on for years crashed out
and
Windows needed to be re-installed from scratch.
Now, using the same install CD and the Same FE (MDB) and BE (MDE) we
are
getting Runtime crashes no matter if we click on cmdContinue to open
another frm or to simply click Exit to shut the app down.

Andy


Andy,

Are you saying that when not on stand alone machines everyone is
accessing the same front end? I think more details are going to be
needed to figure out exactly what your issue is.

--
Gina Whipp

"I feel I have been denied critical, need to know, information!" -
Tremors II

Gentlemen;

Thank You all for reading and replying to my post.

Created this mdb front end and mde back using Office 2000
Developer.

Its not that Dbase doesn't run At All. It does run on other
machines,
(all
Stand Alones).

The Crash happens at the "Log In" frm.

No matter if the User clicks "Continue" or the cmdExit OnClick
Event is:
Private Sub cmdExit_Click()
DoCmd.Quit
End Sub

Access Crashes due to a RunTime Error.

Why? How do I discover what is crashing? What is causing it?

Again Thank You for taking the time to read and reply to my post.

Andy


"a a r o n . k e m p f @ g m a i l . c o m"
<[email protected]>
wrote in message
Rob;

Maybe if you knew how to work the worlds most popular database,
then
maybe- just maybe- you wouldn't be stuck wiht a paperweight-sized
database






On Dec 29, 9:50 pm, Robert Morley
<[email protected]>
wrote:
Tony Toews [MVP] wrote:

Please ignore Aaron Kempf's posting as he responds with SQL
Server
and
ADPs as the answer even when that would have no resemblance to
the
problem.

Tony

What's funny about this is that in the case I spoke of, I was
using an
A2K
ADP.

Rob

 

[Andy]

Gina;

Already using that code.

It doesn't generate an Error Message. Just gets a RunTime Crash.

 

[Gina Whipp]

Sorry I couldn't help! Maybe we will both learn something new, once you get
a reply to that post!!!!

--
Gina Whipp

"I feel I have been denied critical, need to know, information!" - Tremors
II

Gina;

Thank You for Your time.

Have tried un-install / re-install at least 3 times already on this
particular computer. Still No Go.

The question is simply: Why does "DoCmd.Quit" cause a Runtime Crash?

Going to wait a few more hours for anymore replies to this post then going
to Post again with the subject line being that question.
Why does "DoCmd.Quit" cause a Runtime Crash?

Again Thank All for reading and replying to this post.

Happy New Year.

Andy

Andy,

I am stumped. I guess I would try uninstalling and reinstalling and/or
recreating the button. But after that I am not sure what to try next.

--
Gina Whipp

"I feel I have been denied critical, need to know, information!" -
Tremors II

Its the same Microsoft ActiveX Data Objects 2.8 Library being used on
the test computers that do run the app correctly as it is on the
re-built computer.
Same order. Same files. MDE / MDB. Same install CD.

Found a note that said originally it was Microsoft ActiveX Data Objects
2.1 Library.

Changed it back to 2.1 but it still gets Runtime Crash on the re-built
computer.

Andy



And they are the same for the machines that work and the one that
doesn't work and in the same order?

--
Gina Whipp

"I feel I have been denied critical, need to know, information!" -
Tremors II

Yes have Admin rights.

The references are correct. Meaning they are the same as when the
Runtime app was originally installed in 2007.
Visual Basic for Applications
Microsoft Access 9.0 Object Library
OLE Automation
Microsoft ActiveX Data Objects 2.8 Library
Microsoft DAO 3.6 Object Library
Microsoft Word 9.0 Object Library
Microsoft Visual Basic for Applications Extensibility 5.3

Andy

Is it possible for you to check the References on a machine it does
run on to the machine it doesn't run on? Do you have Admin rights to
this database?

--
Gina Whipp

"I feel I have been denied critical, need to know, information!" -
Tremors II
Gina;

Thank You.

All updates and patches in place for both Windows XP Pro & Office
including Access Runtime.

There is no network path.
We are trying to Re_Install on a stand alone computer using the same
install
CD that originally installed a RunTime version of Access 2000 (ART)
and ran
an app that was created using Office Developer 2000.

This particular computer had to be "Re-built". Windows and
everything else
was re-installed from scratch about 2 weeks ago.

Only One User. No network involved.
The BE is MDE the FE MDB & Secured.MDW with User Level Permissions.

The Splash Screen displays correctly and the Login frm allows the
User to
enter a password. So I know Access Runtime is installed correctly.

Its when the User clicks on either cmdLogin or cmdExit is when the
crash
occurs.

The frmLogin has 3 Controls:
txtPwordAsk (User enters the password)
UnBound.

cmdLogin
OnClick:
If Me![txtPwordAsk] = (DLookup("[MyPWord]", "tblMain")) Or
Me![txtPwordAsk] = "*SpecialPWord*" Then
DoCmd.OpenForm "frmMain"
DoCmd.Close acForm, "frmLogin"
Else
Msg = MsgBox("That is not the correct Password." & vbCrLf & _
"Please enter the Password once more.", vbOKOnly + vbInformation,
"OurCompany")
Me![txtPwordAsk] = Null
Me![txtPwordAsk] = Null ' Don't know why this line is here twice.
DoCmd.GoToControl "txtPwordAsk"
End If

cmdExit
OnClick:
DoCmd.Quit

This same code has been used on that re-built stand alone since 2007.

With this current re-install of Windows and all applications when the
User clicks on either cmdButton an Access Runtime Crash occurs.

With or Without PWord typed in when the User clicks on either
cmdButton an Access Runtime Crash occurs and Access shutsdown.

Have seen this same type of crash before when the permissions for a
frm were not granted to the User. Verified the User had Open/Run
permissions for frmLogin. Also gave it Read Design permission.
Still crashed in same places.

What is odd to me is that it is even getting a RunTime crash with:
cmdExit OnClick: DoCmd.Quit
DoCmd.Quit should if nothing else close the app without crashing.

Lady and Gentlemen is there anymore information You might need to
help You help me to overcome this obstacle?

Thank You for taking the time to read this post.

Andy


Andy,

Let's start with obvious... Are all the patches for Windows and
Office
applied? Then check network paths to make sure they are set up the
same.
And why are installing a seperate BE, isn't everyone connected to
the same
BE?

--
Gina Whipp

"I feel I have been denied critical, need to know, information!" -
Tremors
II

Gina;

Thank You for reading and replying to my post.

What I mean is that I have installed the app on other computers to
test
the installation. All of those machines are stand alones as is the
computer that is getting the Runtime crash.

The computer that the app has been running on for years crashed out
and
Windows needed to be re-installed from scratch.
Now, using the same install CD and the Same FE (MDB) and BE (MDE)
we are
getting Runtime crashes no matter if we click on cmdContinue to
open
another frm or to simply click Exit to shut the app down.

Andy


Andy,

Are you saying that when not on stand alone machines everyone is
accessing the same front end? I think more details are going to
be
needed to figure out exactly what your issue is.

--
Gina Whipp

"I feel I have been denied critical, need to know, information!" -
Tremors II

Gentlemen;

Thank You all for reading and replying to my post.

Created this mdb front end and mde back using Office 2000
Developer.

Its not that Dbase doesn't run At All. It does run on other
machines,
(all
Stand Alones).

The Crash happens at the "Log In" frm.

No matter if the User clicks "Continue" or the cmdExit OnClick
Event is:
Private Sub cmdExit_Click()
DoCmd.Quit
End Sub

Access Crashes due to a RunTime Error.

Why? How do I discover what is crashing? What is causing it?

Again Thank You for taking the time to read and reply to my post.

Andy


"a a r o n . k e m p f @ g m a i l . c o m"
<[email protected]>
wrote in message
Rob;

Maybe if you knew how to work the worlds most popular database,
then
maybe- just maybe- you wouldn't be stuck wiht a paperweight-sized
database






On Dec 29, 9:50 pm, Robert Morley
<[email protected]>
wrote:
Tony Toews [MVP] wrote:

Please ignore Aaron Kempf's posting as he responds with SQL
Server
and
ADPs as the answer even when that would have no resemblance to
the
problem.

Tony

What's funny about this is that in the case I spoke of, I was
using an
A2K
ADP.

Rob

 

[Tony Toews [MVP]]

I've remove the last reference, VBA for Extensibility.. It's
automatically inserted by Access when you convert a database to a
newer version. Although that could've been from A97 to A2000 or
something like that. IOW quite a while ago.

Tony
--
Tony Toews, Microsoft Access MVP
Please respond only in the newsgroups so that others can
read the entire thread of messages.
Microsoft Access Links, Hints, Tips & Accounting Systems at
http://www.granite.ab.ca/accsmstr.htm
Tony's Microsoft Access Blog - http://msmvps.com/blogs/access/

 

[Tony Toews [MVP]]

Already using that code.

Actually you're not based on your initial posting. Gina's code has
the error handling in it. Which, if inserted in the may give us a
better error message.

It doesn't generate an Error Message. Just gets a RunTime Crash.

By runtime crash you mean
"Execution of this application has stopped due to a run-time error."
"The application can't continue and will be shut down."

If so inserting the error handling as per Gina's suggestion will
likely result in a more meaningful message.

Tony
--
Tony Toews, Microsoft Access MVP
Please respond only in the newsgroups so that others can
read the entire thread of messages.
Microsoft Access Links, Hints, Tips & Accounting Systems at
http://www.granite.ab.ca/accsmstr.htm
Tony's Microsoft Access Blog - http://msmvps.com/blogs/access/

 

[Andy]

Tony;

Thank You for Your replies.

At first the full code (Included Below) wasn't included because I didn't
want to make You kind people read a lot of redundancies.

The Error Traps have been in place since the app was originally created.
Each trap does 2 things. Shows the Access Internal Error msg and displays
the name of the Command that failed.
Neither displays any message.
All that shows is:
"Execution of this application has stopped due to a run-time error."
"The application can't continue and will be shut down."

As for Your other reply:

"I've remove the last reference, VBA for Extensibility.. It's
automatically inserted by Access when you convert a database to a
newer version. Although that could've been from A97 to A2000 or
something like that. IOW quite a while ago."

The application was started and completed in Office Developer 2000 using
Access 2000.
So it has never been brought forward from an older version of Access.
We did re-install the app once before on the same computer. The machine was
"Rebuilt" from scratch about a year ago.

Tony, one last thing. What is "IOW"?

Andy

Full Code for both Commands in frmLogin

Private Sub cmdExit_Click()
On Error GoTo Err_cmdExit_Click
Dim Msg, Style, Title, Help, Ctxt

DoCmd.Quit

Exit_cmdExit_Click:
Exit Sub

Err_cmdExit_Click:
Msg = MsgBox("Either:" & vbCrLf & Error$ & vbCrLf & vbCrLf & _
"Or this command ''cmdExit_Click'' doesn't understand Your input. "
& vbCrLf & _
" Click the OK button" & vbCrLf & _
" Try the steps again." & vbCrLf & _
" If You Need Help, click the OK button then press the F1 key.",
vbOKOnly + vbCritical, "OurCompany")
Resume Exit_cmdExit_Click
End Sub

Private Sub cmdLogin_Click()
On Error GoTo Err_cmdLogin_Click
Dim strInput As String
Dim Msg, Style, Title, Help, Ctxt

If Me![txtPwordAsk] = (DLookup("[MyPWord]", "tblMain")) Or
Me![txtPwordAsk] = "*SpecialPWord*" Then
DoCmd.OpenForm "frmMain"
DoCmd.Close acForm, "frmLogin"
Else
Msg = MsgBox("That is not the correct Password." & vbCrLf & _
"Please enter the Password once more.", vbOKOnly + vbInformation,
"OurCompany")
Me![txtPwordAsk] = Null
Me![txtPwordAsk] = Null ' Don't know why this line is here twice.
DoCmd.GoToControl "txtPwordAsk"
End If

Exit_cmdLogin_Click:
Exit Sub

Err_cmdLogin_Click:
Msg = MsgBox("Either:" & vbCrLf & Error$ & vbCrLf & vbCrLf & _
"Or this command ''cmdLogin_Click'' doesn't understand Your input. "
& vbCrLf & _
" Click the OK button" & vbCrLf & _
" Try the steps again." & vbCrLf & _
" If You Need Help, click the OK button; then press the F1 key.",
vbOKOnly + vbCritical, "OurCompany")
Resume Exit_cmdLogin_Click
End Sub

 

[Tony Toews [MVP]]

At first the full code (Included Below) wasn't included because I didn't
want to make You kind people read a lot of redundancies.

The Error Traps have been in place since the app was originally created.
Each trap does 2 things. Shows the Access Internal Error msg and displays
the name of the Command that failed.
Neither displays any message.
All that shows is:
"Execution of this application has stopped due to a run-time error."
"The application can't continue and will be shut down."

Then I'm not sure. Is there some code that sets global variables such
as a database or recordset or some such on startup?

"I've remove the last reference, VBA for Extensibility.. It's
automatically inserted by Access when you convert a database to a
newer version. Although that could've been from A97 to A2000 or
something like that. IOW quite a while ago."

The application was started and completed in Office Developer 2000 using
Access 2000.
So it has never been brought forward from an older version of Access.
We did re-install the app once before on the same computer. The machine was
"Rebuilt" from scratch about a year ago.

Fair enough. But have you tried removing that reference anyhow?

Tony, one last thing. What is "IOW"?

In Other Words.

Andy

Full Code for both Commands in frmLogin

Private Sub cmdExit_Click()
On Error GoTo Err_cmdExit_Click
Dim Msg, Style, Title, Help, Ctxt

Those Dims are automatically Variant type of fields not that that
should make a difference in this problem.

Msg = MsgBox("Either:" & vbCrLf & Error$ & vbCrLf & vbCrLf & _
"Or this command ''cmdExit_Click'' doesn't understand Your input. "
& vbCrLf & _
" Click the OK button" & vbCrLf & _
" Try the steps again." & vbCrLf & _
" If You Need Help, click the OK button then press the F1 key.",
vbOKOnly + vbCritical, "OurCompany")

For now just comment the above lines and put in

msgbox Err.description

and see what happens.

Tony
--
Tony Toews, Microsoft Access MVP
Please respond only in the newsgroups so that others can
read the entire thread of messages.
Microsoft Access Links, Hints, Tips & Accounting Systems at
http://www.granite.ab.ca/accsmstr.htm
Tony's Microsoft Access Blog - http://msmvps.com/blogs/access/

 

[Andy]

Tony;

Thank You again for replying.

Re: global variables... Recordset.
Do remember somewhere along the line getting the same type of crash w/
Recordset.Requery. Not the case in this situation.

Also not sure I understand "global variables". Searched Help for "global
variables" and "set global variables". Nothing obvious that would pertain
to this.

Will remove VBA for Extensibility.

Tony; think we're on the wrong path. We have a existing Install CD. The
same CD that installed this application including "ART" successfully twice
before. Once shortly after the computer was purchased. Once again when the
machine had to be "Rebuilt" about a year and a half ago. This time the app
starts and gets a Run-Time crash at a fundamental command: DoCmd.Quit.

Thinking something changed with the machine. Microsoft has brought out a
lot of patches for Windows XP in a year and a half and ART has been updated.

In the early 1990s a local company was selling a DOS based DBASE Program.
Friends with the owners of 3 companies that bought it. I was able to bring
it Forward all the way to early Windows XP machines. Each time a new
computer was needed the DOS program was copied onto the H/Drive and it ran.
Then on the last 2 new computers, (1-Dell, 1-H/P) the program won't even
open. When the Shortcut Icon is dbl-clicked to start the program all You
see on the screen is a "Blink" and the program closes. Set the
"Compatibility" options for the shortcut and still the same thing. Called
Dell and H/P. Got the "It isn't our program" answer.

In both cases don't think its the program. Think an update to Windows
changed "Something". Same CD. Same Install.

Your thoughts?

Andy

 

[Gina Whipp]

Andy,

Just had a thought... I wonder on the new machines is it 64 bit and the
older machines 32 bit?

 

[Andy]

Gina;

Thank You for this latest "Thought".
No. Same computer. Same CD. Same Install.

Your original suggestion worked. Re-Install, Re-Install, Re-Install.

Had sent an e-mail to microsoft. Subject: Don't understand why would
DoCmd.Quit get a run-time error.
Got the standard "Warranty support is no longer available for Access 2000."

DoCmd.Quit is not limited to Access 2000. Its still used today.

Got thinking about a reply I sent to Tony Toews.
"Think an update to Windows
Un-Installed and Re-Installed 2 more times. Each time tried to open the MDB
got the same Runtime Crash.

The third Un-Install and Re-Install worked! No more crashes.

Don't know if the first Install some how "Blinked" and then left something
behind. Nothing else has changed.

As of this moment if I had to advise someone on what to do in this
situation: "Go with Gina's suggestion, Un-Install - Re-Install,
Un-Install - Re-Install, Un-Install - Re-Install, Un-Install - Re-Install,
Un-Install - Re-Install until it works." Ha!

Thank You all again for Your kindness and replies.

Andy

 

[Gina Whipp]

Glad it worked, sorry it took so much work!
Glad it worked, sorry it took so much work!
Glad it worked, sorry it took so much work!
etc...

 

[RoyVidar]

DoCmd.Quit is not limited to Access 2000. Its still used today.

But, the help file, at least dating back to the 2000 version (probably
earlier), says

"Remarks

The Quit method of the DoCmd object was added to provide backward
compatibility for running the Quit action in Visual Basic code in
Microsoft Access 95. It's recommended that you use the existing Quit
method of the Application object instead."

http://msdn.microsoft.com/en-us/library/aa221549(office.11).aspx

So

Application.Quit over DoCmd.Quit. Don't know how that equates into
this discussion, though.

 

[Andy]

Roy;

Thank You for Your reply.

Will change code to "the existing Quit method of the Application object
instead.".

The app is running. Never found out why it didn't.

4 to 5 Install, Un-Install, Installs worked.

As the old folks used to say "No Rhyme Nor Reason".

Thank You again.

Andy

 

[david]

The question is simply: Why does "DoCmd.Quit" cause a Runtime Crash?

Because some object is closing in the wrong order.

(david)

Gina;

Thank You for Your time.

Have tried un-install / re-install at least 3 times already on this
particular computer. Still No Go.

The question is simply: Why does "DoCmd.Quit" cause a Runtime Crash?

Going to wait a few more hours for anymore replies to this post then going
to Post again with the subject line being that question.
Why does "DoCmd.Quit" cause a Runtime Crash?

Again Thank All for reading and replying to this post.

Happy New Year.

Andy

Andy,

I am stumped. I guess I would try uninstalling and reinstalling and/or
recreating the button. But after that I am not sure what to try next.

--
Gina Whipp

"I feel I have been denied critical, need to know, information!" -
Tremors II

Its the same Microsoft ActiveX Data Objects 2.8 Library being used on
the test computers that do run the app correctly as it is on the
re-built computer.
Same order. Same files. MDE / MDB. Same install CD.

Found a note that said originally it was Microsoft ActiveX Data Objects
2.1 Library.

Changed it back to 2.1 but it still gets Runtime Crash on the re-built
computer.

Andy



And they are the same for the machines that work and the one that
doesn't work and in the same order?

--
Gina Whipp

"I feel I have been denied critical, need to know, information!" -
Tremors II

Yes have Admin rights.

The references are correct. Meaning they are the same as when the
Runtime app was originally installed in 2007.
Visual Basic for Applications
Microsoft Access 9.0 Object Library
OLE Automation
Microsoft ActiveX Data Objects 2.8 Library
Microsoft DAO 3.6 Object Library
Microsoft Word 9.0 Object Library
Microsoft Visual Basic for Applications Extensibility 5.3

Andy

Is it possible for you to check the References on a machine it does
run on to the machine it doesn't run on? Do you have Admin rights to
this database?

--
Gina Whipp

"I feel I have been denied critical, need to know, information!" -
Tremors II
Gina;

Thank You.

All updates and patches in place for both Windows XP Pro & Office
including Access Runtime.

There is no network path.
We are trying to Re_Install on a stand alone computer using the same
install
CD that originally installed a RunTime version of Access 2000 (ART)
and ran
an app that was created using Office Developer 2000.

This particular computer had to be "Re-built". Windows and
everything else
was re-installed from scratch about 2 weeks ago.

Only One User. No network involved.
The BE is MDE the FE MDB & Secured.MDW with User Level Permissions.

The Splash Screen displays correctly and the Login frm allows the
User to
enter a password. So I know Access Runtime is installed correctly.

Its when the User clicks on either cmdLogin or cmdExit is when the
crash
occurs.

The frmLogin has 3 Controls:
txtPwordAsk (User enters the password)
UnBound.

cmdLogin
OnClick:
If Me![txtPwordAsk] = (DLookup("[MyPWord]", "tblMain")) Or
Me![txtPwordAsk] = "*SpecialPWord*" Then
DoCmd.OpenForm "frmMain"
DoCmd.Close acForm, "frmLogin"
Else
Msg = MsgBox("That is not the correct Password." & vbCrLf & _
"Please enter the Password once more.", vbOKOnly + vbInformation,
"OurCompany")
Me![txtPwordAsk] = Null
Me![txtPwordAsk] = Null ' Don't know why this line is here twice.
DoCmd.GoToControl "txtPwordAsk"
End If

cmdExit
OnClick:
DoCmd.Quit

This same code has been used on that re-built stand alone since 2007.

With this current re-install of Windows and all applications when the
User clicks on either cmdButton an Access Runtime Crash occurs.

With or Without PWord typed in when the User clicks on either
cmdButton an Access Runtime Crash occurs and Access shutsdown.

Have seen this same type of crash before when the permissions for a
frm were not granted to the User. Verified the User had Open/Run
permissions for frmLogin. Also gave it Read Design permission.
Still crashed in same places.

What is odd to me is that it is even getting a RunTime crash with:
cmdExit OnClick: DoCmd.Quit
DoCmd.Quit should if nothing else close the app without crashing.

Lady and Gentlemen is there anymore information You might need to
help You help me to overcome this obstacle?

Thank You for taking the time to read this post.

Andy


Andy,

Let's start with obvious... Are all the patches for Windows and
Office
applied? Then check network paths to make sure they are set up the
same.
And why are installing a seperate BE, isn't everyone connected to
the same
BE?

--
Gina Whipp

"I feel I have been denied critical, need to know, information!" -
Tremors
II

Gina;

Thank You for reading and replying to my post.

What I mean is that I have installed the app on other computers to
test
the installation. All of those machines are stand alones as is the
computer that is getting the Runtime crash.

The computer that the app has been running on for years crashed out
and
Windows needed to be re-installed from scratch.
Now, using the same install CD and the Same FE (MDB) and BE (MDE)
we are
getting Runtime crashes no matter if we click on cmdContinue to
open
another frm or to simply click Exit to shut the app down.

Andy


Andy,

Are you saying that when not on stand alone machines everyone is
accessing the same front end? I think more details are going to
be
needed to figure out exactly what your issue is.

--
Gina Whipp

"I feel I have been denied critical, need to know, information!" -
Tremors II

Gentlemen;

Thank You all for reading and replying to my post.

Created this mdb front end and mde back using Office 2000
Developer.

Its not that Dbase doesn't run At All. It does run on other
machines,
(all
Stand Alones).

The Crash happens at the "Log In" frm.

No matter if the User clicks "Continue" or the cmdExit OnClick
Event is:
Private Sub cmdExit_Click()
DoCmd.Quit
End Sub

Access Crashes due to a RunTime Error.

Why? How do I discover what is crashing? What is causing it?

Again Thank You for taking the time to read and reply to my post.

Andy


"a a r o n . k e m p f @ g m a i l . c o m"
<[email protected]>
wrote in message
Rob;

Maybe if you knew how to work the worlds most popular database,
then
maybe- just maybe- you wouldn't be stuck wiht a paperweight-sized
database






On Dec 29, 9:50 pm, Robert Morley
<[email protected]>
wrote:
Tony Toews [MVP] wrote:

Please ignore Aaron Kempf's posting as he responds with SQL
Server
and
ADPs as the answer even when that would have no resemblance to
the
problem.

Tony

What's funny about this is that in the case I spoke of, I was
using an
A2K
ADP.

Rob

 

[david]

According to the old documentation, "err.Description" reports some
COM errors that Error$ is not able to report.

(david)

 

[EAB1977]

If I could put my 2 cents in...

If your using the above code and not getting anything in return, my
guess is that your error is somewhere else in your database. These can
be hard to find, as I have had to track these down.

Make sure you use Error Handling everywhere, but even then that
doesn't help sometimes.

My next guess would be to try steping through your code one by one on
a fully licenced Access machine using someone else's login.

 

[Andy]

David;

Thank You and everyone else for Your kindness.

The app is running on the PC and correctly after several Installs /
Un-Installs / Re-Installs.

I will try "err.Description" in the future.

Andy

 

[Jack Cannon]

Andy,

I also experienced problems with Access 2000 crashing with no apparent
reason and in conditions that were totally illogical. That did not happen
after upgrading to 2002. A common factor with the 2000 crashes was that it
appeared to start happening when the file reached a certain critical size
(after compacting and repairing). That size was about 10K. Whether the size
or even the version was a factor is unknown. I can only say with confidence
that the problem did go away after the upgrade to 2002.

Jack Cannon