A2K Runtime Crashes on DoCmd.Quit

[Andy]

Hi;

Using A2K Runtime on XP Pro PC. Have all of the updates for XP and Access
Runtime including SP-3 for both.

The app opens to frmLogin correctly. On that form there are 2 cmd buttons.
Continue & Exit.

Can log in as USER or sa, (System Administrator) but when clicking either
cmd button get Access Runtime Crash.

"Execution of this application has stopped due to a run-time error."
"The application can't continue and will be shut down."
Only has OK button.

The cmdExit OnClick Event is:
Private Sub cmdExit_Click()
DoCmd.Quit
End Sub

Don't understand why would get a run-time error on DoCmd.Quit.

The MDB does work correctly on the machine that created it. Even opening it
as the User in Runtime Version emulation.

This Computer's Shortcut for Runtime test Target: "C:\Program
Files\Microsoft Office\Office\MSACCESS.EXE" "C:\CoDBase\CoDBase.mdb" /WRKGRP
"C:\CoDBase\Secured.mdw" /runtime /excl
Start In: C:\CoDBase\

On computer with only Access Runtime:
Shortcut Target: "C:\Program Files\Microsoft Office\ART\Office\MSACCESS.EXE"
"C:\CoDBase\CoDBase.mdb" /WRKGRP "C:\CoDBase\Secured.mdw" /excl
Start In: C:\CoDBase\

The permissions for frmLogin is:
sa = Open/Run, Read Design, Modify Design & Administer.

For the User: Open/Run

The User has permissions to Open / Run and Open Exclusive for the Current
Database.
Already re-ran Security Wizard. Thought maybe Secured.mdw was corrupt.

Would someone be so kind and point me in the proper direction to overcome
this obstacle?

Thank You for taking the time to read this post.

Andy

 

[Robert Morley]

Hi;

Using A2K Runtime on XP Pro PC. Have all of the updates for XP and Access
Runtime including SP-3 for both.

The app opens to frmLogin correctly. On that form there are 2 cmd buttons.
Continue & Exit.

Can log in as USER or sa, (System Administrator) but when clicking either
cmd button get Access Runtime Crash.

"Execution of this application has stopped due to a run-time error."
"The application can't continue and will be shut down."
Only has OK button.

The cmdExit OnClick Event is:
Private Sub cmdExit_Click()
DoCmd.Quit
End Sub

Don't understand why would get a run-time error on DoCmd.Quit.

The MDB does work correctly on the machine that created it. Even opening it
as the User in Runtime Version emulation.

This Computer's Shortcut for Runtime test Target: "C:\Program
Files\Microsoft Office\Office\MSACCESS.EXE" "C:\CoDBase\CoDBase.mdb" /WRKGRP
"C:\CoDBase\Secured.mdw" /runtime /excl
Start In: C:\CoDBase\

On computer with only Access Runtime:
Shortcut Target: "C:\Program Files\Microsoft Office\ART\Office\MSACCESS.EXE"
"C:\CoDBase\CoDBase.mdb" /WRKGRP "C:\CoDBase\Secured.mdw" /excl
Start In: C:\CoDBase\

The permissions for frmLogin is:
sa = Open/Run, Read Design, Modify Design & Administer.

For the User: Open/Run

The User has permissions to Open / Run and Open Exclusive for the Current
Database.
Already re-ran Security Wizard. Thought maybe Secured.mdw was corrupt.

Would someone be so kind and point me in the proper direction to overcome
this obstacle?

Thank You for taking the time to read this post.

Andy

I remember having some really wonky conditions in A2K under which the app
would crash when closing, though they weren't identical to your, since I
remember it only occurred when closing the form with the X but would work
fine from a command button.

First of all, try this under XP/2003/2007 if you have any of those
available, just to see if it works there or not. Mine worked under all
future versions and only failed under 2000 (never tried the runtime version,
mind you).

What I would try next are "stupid" workarounds...for instance, from your
Click procedure, call a sub that'll close the form (or maybe all forms),
loop in a DoEvents loop for half a second, then quit. See if there's
anything of that nature that works for you. Failing that, try using the
Windows API to close your app and see if that works (I don't remember
exactly how to do that, but I know it's not hard...I'm sure someone can post
it if you need).

Good luck!


Rob

 

[a a r o n . k e m p f]

run away from Jet, it's not reliable enough for every day usage.

Only if you move to SQL Server can you avoid these sorts of headaches.

-Aaron

 

[Tony Toews [MVP]]

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
--
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/

 

[a a r o n . k e m p f]

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

----------------------------------------------------------------------------------------
Access, however, is not perfect. Performance degrades significantly as
the database size increases. The database is also prone to corruption.
Finally, starting with an Access database has tempted many developers
to do a dangerous thing. Sometimes a single-user application becomes
popular enough that there's a desire for it to be used by multiple
simultaneous users. The temptation is to just move the Access database
file to a network share, copy the application to multiple machines,
and let many users connect simultaneously. Access performance drops
off quickly with multiple users, and it's highly unlikely that an
application that was designed for a single user will work reliably
with concurrent users.

http://msdn.microsoft.com/en-us/library/aa730870(VS.80).aspx

 

[Robert Morley]

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

 

[a a r o n . k e m p f]

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

 

[Andy]

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


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

 

[Gina Whipp]

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.

 

[Andy]

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]

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

 

[GenlAccess]

Please ignore Aaron Kempf's posting

First smart thing the boy's said in all the time he's been here!

as he responds with JET as the
answer even when that would have
no resemblance to the problem.

But still has no grasp on reality... can't even remember what he posted
himself. Sad, surely sad.

Genl Access

 

[Andy]

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]

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]

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

 

[Andy]

Note: Microsoft ActiveX Data Objects 2.8 Library was originally Microsoft
ActiveX Data Objects 2.1 Library.

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]

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]

Does this mean that the others have 2.1 and this one has 2.8?

--
Gina Whipp

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

Note: Microsoft ActiveX Data Objects 2.8 Library was originally Microsoft
ActiveX Data Objects 2.1 Library.

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]

What is the rest of the code behind the LogIn menu?

--
Gina Whipp

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

Note: Microsoft ActiveX Data Objects 2.8 Library was originally Microsoft
ActiveX Data Objects 2.1 Library.

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]

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