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

Because some object is closing in the wrong order.

(david)

"Andy" wrote in message
...
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



"Gina Whipp" wrote in message
...
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
"Andy" wrote in message
...
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



"Gina Whipp" wrote in message
...
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
"Andy" wrote in message
...

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

"Gina Whipp" wrote in message
...
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
"Andy" wrote in message
...
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


"Gina Whipp" wrote in message
...
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

"Andy" wrote in message
...
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


"Gina Whipp" wrote in message
...
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

"Andy" wrote in message
...
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"

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

wrote:
Tony Toews [MVP] wrote:
"Andy" 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