According to the old documentation, "err.Description" reports some
COM errors that Error$ is not able to report.
(david)
"Gina Whipp" wrote in message
...
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
--
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