A2K Runtime Crashes on DoCmd.Quit "Andy" <DontWant[ at ]email.com> 12/24/2008 8:50:03 PM 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

Re: A2K Runtime Crashes on DoCmd.Quit Robert Morley <rmorley[ at ]N0.Freak1n.sparn.magma.ca> 12/24/2008 11:10:13 PM Andy wrote: [Quoted Text] > 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

Re: A2K Runtime Crashes on DoCmd.Quit "a a r o n . k e m p f [ at ] g m a i l . c o m" <aaron.kempf[ at ]gmail.com> 12/27/2008 2:29:31 AM 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 On Dec 24, 12:50 pm, "Andy" <DontW...[ at ]email.com> wrote: [Quoted Text] > 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

Re: A2K Runtime Crashes on DoCmd.Quit "Tony Toews [MVP]" <ttoews[ at ]telusplanet.net> 12/27/2008 3:51:53 AM "Andy" <DontWant[ at ]email.com> 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 -- 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/

Re: A2K Runtime Crashes on DoCmd.Quit "a a r o n . k e m p f [ at ] g m a i l . c o m" <aaron.kempf[ at ]gmail.com> 12/27/2008 4:54:35 PM 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 ---------------------------------------------------------------------------------------- On Dec 26, 7:51 pm, "Tony Toews [MVP]" <tto...[ at ]telusplanet.net> wrote: [Quoted Text] > "Andy" <DontW...[ at ]email.com> 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 > -- > 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 athttp://www.granite.ab.ca/accsmstr.htm >    Tony's Microsoft Access Blog -http://msmvps.com/blogs/access/

Re: A2K Runtime Crashes on DoCmd.Quit Robert Morley <rmorley[ at ]N0.Freak1n.sparn.magma.ca> 12/30/2008 5:50:21 AM Tony Toews [MVP] wrote: [Quoted Text] > "Andy" <DontWant[ at ]email.com> 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

Re: A2K Runtime Crashes on DoCmd.Quit "a a r o n . k e m p f [ at ] g m a i l . c o m" <aaron.kempf[ at ]gmail.com> 12/30/2008 3:16:11 PM 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 <rmor...[ at ]N0.Freak1n.sparn.magma.ca> wrote: [Quoted Text] > Tony Toews [MVP] wrote: > > "Andy" <DontW...[ at ]email.com> 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

Re: A2K Runtime Crashes on DoCmd.Quit "Andy" <DontWant[ at ]email.com> 12/30/2008 3:39:11 PM 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 [ at ] g m a i l . c o m" <aaron.kempf[ at ]gmail.com> wrote in message news:52cc81fc-1c5c-4ec6-abab-e0caf87b0e84[ at ]b41g2000pra.googlegroups.com... 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 <rmor...[ at ]N0.Freak1n.sparn.magma.ca> wrote: [Quoted Text] > Tony Toews [MVP] wrote: > > "Andy" <DontW...[ at ]email.com> 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

Re: A2K Runtime Crashes on DoCmd.Quit "Gina Whipp" <NotInterested[ at ]InViruses.com> 12/30/2008 3:53:31 PM 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" <DontWant[ at ]email.com> wrote in message news:ONsTFTpaJHA.4504[ at ]TK2MSFTNGP04.phx.gbl... [Quoted Text] > 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 [ at ] g m a i l . c o m" <aaron.kempf[ at ]gmail.com> wrote > in message > news:52cc81fc-1c5c-4ec6-abab-e0caf87b0e84[ at ]b41g2000pra.googlegroups.com... > 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 <rmor...[ at ]N0.Freak1n.sparn.magma.ca> > wrote: >> Tony Toews [MVP] wrote: >> > "Andy" <DontW...[ at ]email.com> 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 > >

Re: A2K Runtime Crashes on DoCmd.Quit "Andy" <DontWant[ at ]email.com> 12/31/2008 12:02:37 AM 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" <NotInterested[ at ]InViruses.com> wrote in message news:%23rLzFbpaJHA.1704[ at ]TK2MSFTNGP05.phx.gbl... [Quoted Text] > 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" <DontWant[ at ]email.com> wrote in message > news:ONsTFTpaJHA.4504[ at ]TK2MSFTNGP04.phx.gbl... >> 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 [ at ] g m a i l . c o m" <aaron.kempf[ at ]gmail.com> wrote >> in message >> news:52cc81fc-1c5c-4ec6-abab-e0caf87b0e84[ at ]b41g2000pra.googlegroups.com... >> 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 <rmor...[ at ]N0.Freak1n.sparn.magma.ca> >> wrote: >>> Tony Toews [MVP] wrote: >>> > "Andy" <DontW...[ at ]email.com> 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 >> >> > >

Re: A2K Runtime Crashes on DoCmd.Quit "Gina Whipp" <NotInterested[ at ]InViruses.com> 12/31/2008 12:15:56 AM 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" <DontWant[ at ]email.com> wrote in message news:uGDHastaJHA.1676[ at ]TK2MSFTNGP03.phx.gbl... [Quoted Text] > 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" <NotInterested[ at ]InViruses.com> wrote in message > news:%23rLzFbpaJHA.1704[ at ]TK2MSFTNGP05.phx.gbl... >> 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" <DontWant[ at ]email.com> wrote in message >> news:ONsTFTpaJHA.4504[ at ]TK2MSFTNGP04.phx.gbl... >>> 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 [ at ] g m a i l . c o m" <aaron.kempf[ at ]gmail.com> >>> wrote in message >>> news:52cc81fc-1c5c-4ec6-abab-e0caf87b0e84[ at ]b41g2000pra.googlegroups.com... >>> 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 <rmor...[ at ]N0.Freak1n.sparn.magma.ca> >>> wrote: >>>> Tony Toews [MVP] wrote: >>>> > "Andy" <DontW...[ at ]email.com> 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 >>> >>> >> >> > >

Re: A2K Runtime Crashes on DoCmd.Quit GenlAccess 12/31/2008 2:50:00 AM "a a r o n . k e m p f [ at ] g m a i l . c o" wrote: > 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

Re: A2K Runtime Crashes on DoCmd.Quit "Andy" <DontWant[ at ]email.com> 12/31/2008 4:48:08 PM This is a multi-part message in MIME format. ------=_NextPart_000_0024_01C96B3D.A67D5AE0 Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: quoted-printable 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=20 CD that originally installed a RunTime version of Access 2000 (ART) and = ran=20 an app that was created using Office Developer 2000. This particular computer had to be "Re-built". Windows and everything = else=20 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=20 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] =3D (DLookup("[MyPWord]", "tblMain")) Or = Me![txtPwordAsk] =3D "*SpecialPWord*" Then DoCmd.OpenForm "frmMain" DoCmd.Close acForm, "frmLogin" Else Msg =3D MsgBox("That is not the correct Password." & vbCrLf & _ "Please enter the Password once more.", vbOKOnly + vbInformation, = "OurCompany") Me![txtPwordAsk] =3D Null Me![txtPwordAsk] =3D 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" <NotInterested[ at ]InViruses.com> wrote in message=20 news:eYHezztaJHA.2640[ at ]TK2MSFTNGP03.phx.gbl... [Quoted Text] > 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.=20 > And why are installing a seperate BE, isn't everyone connected to the = same=20 > BE? > > --=20 > Gina Whipp > > "I feel I have been denied critical, need to know, information!" - = Tremors=20 > II > > "Andy" <DontWant[ at ]email.com> wrote in message=20 > news:uGDHastaJHA.1676[ at ]TK2MSFTNGP03.phx.gbl... >> 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=20 >> the installation. All of those machines are stand alones as is the=20 >> computer that is getting the Runtime crash. >> >> The computer that the app has been running on for years crashed out = and=20 >> Windows needed to be re-installed from scratch. >> Now, using the same install CD and the Same FE (MDB) and BE (MDE) we = are=20 >> getting Runtime crashes no matter if we click on cmdContinue to open=20 >> another frm or to simply click Exit to shut the app down. >> >> Andy >> >> >> "Gina Whipp" <NotInterested[ at ]InViruses.com> wrote in message=20 >> news:%23rLzFbpaJHA.1704[ at ]TK2MSFTNGP05.phx.gbl... >>> Andy, >>> >>> Are you saying that when not on stand alone machines everyone is=20 >>> accessing the same front end? I think more details are going to be=20 >>> needed to figure out exactly what your issue is. >>> >>> --=20 >>> Gina Whipp >>> >>> "I feel I have been denied critical, need to know, information!" -=20 >>> Tremors II >>> >>> "Andy" <DontWant[ at ]email.com> wrote in message=20 >>> news:ONsTFTpaJHA.4504[ at ]TK2MSFTNGP04.phx.gbl... >>>> 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,=20 >>>> (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 [ at ] g m a i l . c o m" <aaron.kempf[ at ]gmail.com> = >>>> wrote in message=20 >>>> = news:52cc81fc-1c5c-4ec6-abab-e0caf87b0e84[ at ]b41g2000pra.googlegroups.com...= >>>> 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 = <rmor...[ at ]N0.Freak1n.sparn.magma.ca> >>>> wrote: >>>>> Tony Toews [MVP] wrote: >>>>> > "Andy" <DontW...[ at ]email.com> wrote: >>>>> >>>>> > Please ignore Aaron Kempf's posting as he responds with SQL = Server=20 >>>>> > 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=20 >>>>> A2K >>>>> ADP. ;) >>>>> >>>>> Rob >>>> >>>> >>> >>> >> >> > >=20 ------=_NextPart_000_0024_01C96B3D.A67D5AE0 Content-Type: text/html; charset="iso-8859-1" Content-Transfer-Encoding: quoted-printable <!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.0 Transitional//EN"> <HTML><HEAD> <META http-equiv=3DContent-Type content=3D"text/html; = charset=3Diso-8859-1"> <META content=3D"MSHTML 6.00.2900.5726" name=3DGENERATOR> <STYLE></STYLE> </HEAD> <BODY> <DIV><FONT face=3DArial size=3D2>Gina;</FONT></DIV> <DIV><FONT face=3DArial size=3D2></FONT> </DIV> <DIV><FONT face=3DArial size=3D2>Thank You.<BR><BR>All updates and = patches in place=20 for both Windows XP Pro & Office including Access = Runtime.<BR><BR>There is=20 no network path.<BR>We are trying to Re_Install on a stand alone = computer using=20 the same install <BR>CD that originally installed a RunTime version of = Access=20 2000 (ART) and ran <BR>an app that was created using Office Developer=20 2000.</FONT></DIV> <DIV><BR><FONT face=3DArial size=3D2>This particular computer had to be=20 "Re-built".  Windows and everything else <BR>was re-installed from = scratch=20 about 2 weeks ago.<BR><BR>Only One User.  No network = involved.<BR>The BE is=20 MDE the FE MDB & Secured.MDW with User Level Permissions.<BR><BR>The = Splash=20 Screen displays correctly and the Login frm allows the User to <BR>enter = a=20 password.  So I know Access Runtime is installed = correctly.<BR><BR>Its when=20 the User clicks on either cmdLogin or cmdExit is when the crash=20 <BR>occurs.</FONT></DIV> <DIV><FONT face=3DArial size=3D2></FONT> </DIV> <DIV><FONT face=3DArial size=3D2>The frmLogin has 3 = Controls:</FONT></DIV> <DIV><FONT face=3DArial size=3D2>txtPwordAsk (User enters the = password)</FONT></DIV> <DIV><FONT face=3DArial size=3D2>UnBound.</FONT></DIV> <DIV><FONT face=3DArial size=3D2></FONT> </DIV> <DIV><FONT face=3DArial size=3D2>cmdLogin</FONT></DIV> <DIV><FONT face=3DArial size=3D2>OnClick:<BR></FONT><FONT face=3DArial = size=3D2>If=20 Me![txtPwordAsk] =3D (DLookup("[MyPWord]", "tblMain")) Or = Me![txtPwordAsk] =3D=20 "*SpecialPWord*" Then<BR></FONT><FONT face=3DArial = size=3D2>   =20 DoCmd.OpenForm "frmMain"<BR>    </FONT><FONT face=3DArial = size=3D2>DoCmd.Close acForm, "frmLogin"<BR></FONT><FONT face=3DArial=20 size=3D2>Else<BR></FONT><FONT face=3DArial size=3D2>    = Msg =3D=20 MsgBox("That is not the correct Password." & vbCrLf & = _<BR></FONT><FONT=20 face=3DArial size=3D2>    "Please enter the Password once = more.",=20 vbOKOnly + vbInformation, "OurCompany")<BR></FONT><FONT face=3DArial=20 size=3D2>    Me![txtPwordAsk] =3D Null<BR></FONT><FONT = face=3DArial=20 size=3D2>    Me![txtPwordAsk] =3D Null  ' Don't know = why this line is here twice.<BR></FONT><FONT face=3DArial=20 size=3D2>    DoCmd.GoToControl = "txtPwordAsk"<BR></FONT><FONT=20 face=3DArial size=3D2>End If</FONT></DIV> <DIV><FONT face=3DArial size=3D2></FONT> </DIV> <DIV><FONT face=3DArial size=3D2>cmdExit</FONT></DIV> <DIV><FONT face=3DArial size=3D2>OnClick:</FONT></DIV> <DIV><FONT face=3DArial size=3D2>    = DoCmd.Quit</FONT></DIV> <DIV><FONT face=3DArial size=3D2></FONT> </DIV> <DIV><FONT face=3DArial size=3D2>This same code has been used on that = re-built stand=20 alone since 2007.</FONT></DIV> <DIV><FONT face=3DArial size=3D2></FONT> </DIV> <DIV><FONT face=3DArial size=3D2>With this current re-install of Windows = and all=20 applications when the User clicks on either cmdButton an Access Runtime = Crash=20 occurs.</FONT></DIV> <DIV><FONT face=3DArial size=3D2></FONT> </DIV> <DIV><FONT face=3DArial size=3D2>With or Without PWord typed in when the = User clicks=20 on either cmdButton an Access Runtime Crash occurs and Access=20 shutsdown.</FONT></DIV> <DIV><FONT face=3DArial size=3D2></FONT> </DIV> <DIV><FONT face=3DArial size=3D2>Have seen this same type of crash = before when the=20 permissions for a frm were not granted to the User.  Verified the = User had=20 Open/Run permissions for frmLogin.  Also gave it Read Design=20 permission.  Still crashed in same places.</FONT><FONT face=3DArial = size=3D2></FONT></DIV> <DIV><FONT face=3DArial size=3D2></FONT> </DIV> <DIV><FONT face=3DArial size=3D2>What is odd to me is that it is even = getting a=20 RunTime crash with: <FONT face=3DArial size=3D2>cmdExit = </FONT><FONT face=3DArial=20 size=3D2>OnClick: </FONT><FONT face=3DArial=20 size=3D2>DoCmd.Quit</FONT></FONT></DIV> <DIV><FONT face=3DArial size=3D2>DoCmd.Quit should if nothing else close = the app=20 without crashing.</FONT></DIV> <DIV><FONT face=3DArial size=3D2></FONT> </DIV> <DIV><FONT face=3DArial size=3D2>Lady and Gentlemen is there anymore = information You=20 might need to help You help me to overcome this obstacle?</FONT></DIV> <DIV><FONT face=3DArial size=3D2></FONT> </DIV> <DIV><FONT face=3DArial size=3D2>Thank You for taking the time to read = this=20 post.</FONT></DIV> <DIV><FONT face=3DArial size=3D2></FONT> </DIV> <DIV><FONT face=3DArial size=3D2>Andy</FONT><BR><BR><BR><FONT = face=3DArial=20 size=3D2>"Gina Whipp" <</FONT><A=20 href=3D"mailto:NotInterested[ at ]InViruses.com"><FONT face=3DArial=20 size=3D2>NotInterested[ at ]InViruses.com</FONT></A><FONT face=3DArial = size=3D2>> wrote=20 in message <BR></FONT><A = href=3D"news:eYHezztaJHA.2640[ at ]TK2MSFTNGP03.phx.gbl"><FONT=20 face=3DArial = size=3D2>news:eYHezztaJHA.2640[ at ]TK2MSFTNGP03.phx.gbl</FONT></A><FONT=20 face=3DArial size=3D2>...<BR>> Andy,<BR>><BR>> Let's start with = obvious...=20 Are all the patches for Windows and Office <BR>> applied?  Then = check=20 network paths to make sure they are set up the same. <BR>> And why = are=20 installing a seperate BE, isn't everyone connected to the same <BR>>=20 BE?<BR>><BR>> -- <BR>> Gina Whipp<BR>><BR>> "I feel I = have been=20 denied critical, need to know, information!" - Tremors <BR>>=20 II<BR>><BR>> "Andy" <</FONT><A = href=3D"mailto:DontWant[ at ]email.com"><FONT=20 face=3DArial size=3D2>DontWant[ at ]email.com</FONT></A><FONT face=3DArial = size=3D2>>=20 wrote in message <BR>> </FONT><A=20 href=3D"news:uGDHastaJHA.1676[ at ]TK2MSFTNGP03.phx.gbl"><FONT face=3DArial=20 size=3D2>news:uGDHastaJHA.1676[ at ]TK2MSFTNGP03.phx.gbl</FONT></A><FONT = face=3DArial=20 size=3D2>...<BR>>> Gina;<BR>>><BR>>> Thank You for = reading and=20 replying to my post.<BR>>><BR>>> What I mean is that I have=20 installed the app on other computers to test <BR>>> the=20 installation.  All of those machines are stand alones as is the=20 <BR>>> computer that is getting the Runtime = crash.<BR>>><BR>>>=20 The computer that the app has been running on for years crashed out and=20 <BR>>> Windows needed to be re-installed from scratch.<BR>>> = Now,=20 using the same install CD and the Same FE (MDB) and BE (MDE) we are = <BR>>>=20 getting Runtime crashes no matter if we click on cmdContinue to open=20 <BR>>> another frm or to simply click Exit to shut the app=20 down.<BR>>><BR>>> Andy<BR>>><BR>>><BR>>> = "Gina=20 Whipp" <</FONT><A href=3D"mailto:NotInterested[ at ]InViruses.com"><FONT = face=3DArial=20 size=3D2>NotInterested[ at ]InViruses.com</FONT></A><FONT face=3DArial = size=3D2>> wrote=20 in message <BR>>> </FONT><A=20 href=3D"news:%23rLzFbpaJHA.1704[ at ]TK2MSFTNGP05.phx.gbl"><FONT face=3DArial = size=3D2>news:%23rLzFbpaJHA.1704[ at ]TK2MSFTNGP05.phx.gbl</FONT></A><FONT = face=3DArial=20 size=3D2>...<BR>>>> Andy,<BR>>>><BR>>>> Are = you saying=20 that when not on stand alone machines everyone is <BR>>>> = accessing the=20 same front end?  I think more details are going to be = <BR>>>>=20 needed to figure out exactly what your issue = is.<BR>>>><BR>>>>=20 -- <BR>>>> Gina Whipp<BR>>>><BR>>>> "I feel I = have=20 been denied critical, need to know, information!" - <BR>>>> = Tremors=20 II<BR>>>><BR>>>> "Andy" <</FONT><A=20 href=3D"mailto:DontWant[ at ]email.com"><FONT face=3DArial=20 size=3D2>DontWant[ at ]email.com</FONT></A><FONT face=3DArial size=3D2>> = wrote in=20 message <BR>>>> </FONT><A=20 href=3D"news:ONsTFTpaJHA.4504[ at ]TK2MSFTNGP04.phx.gbl"><FONT face=3DArial=20 size=3D2>news:ONsTFTpaJHA.4504[ at ]TK2MSFTNGP04.phx.gbl</FONT></A><FONT = face=3DArial=20 size=3D2>...<BR>>>>>=20 Gentlemen;<BR>>>>><BR>>>>> Thank You all for = reading and=20 replying to my post.<BR>>>>><BR>>>>> Created = this mdb=20 front end and mde back using Office 2000=20 Developer.<BR>>>>><BR>>>>> Its not that Dbase = doesn't=20 run At All.  It does run on other machines, <BR>>>>>=20 (all<BR>>>>> Stand = Alones).<BR>>>>><BR>>>>>=20 The Crash happens at the "Log In" = frm.<BR>>>>><BR>>>>>=20 No matter if the User clicks "Continue" or the cmdExit=20 OnClick<BR>>>>> Event is:<BR>>>>> Private Sub=20 cmdExit_Click()<BR>>>>> DoCmd.Quit<BR>>>>> End=20 Sub<BR>>>>><BR>>>>> Access Crashes due to a = RunTime=20 Error.<BR>>>>><BR>>>>> Why?  How do I = discover what=20 is crashing?  What is causing = it?<BR>>>>><BR>>>>>=20 Again Thank You for taking the time to read and reply to my=20 post.<BR>>>>><BR>>>>>=20 Andy<BR>>>>><BR>>>>><BR>>>>> "a a r = o n . k=20 e m p f [ at ] g m a i l . c o m" <</FONT><A=20 href=3D"mailto:aaron.kempf[ at ]gmail.com"><FONT face=3DArial=20 size=3D2>aaron.kempf[ at ]gmail.com</FONT></A><FONT face=3DArial = size=3D2>>=20 <BR>>>>> wrote in message <BR>>>>> </FONT><A=20 href=3D"news:52cc81fc-1c5c-4ec6-abab-e0caf87b0e84[ at ]b41g2000pra.googlegroup= s.com"><FONT=20 face=3DArial=20 size=3D2>news:52cc81fc-1c5c-4ec6-abab-e0caf87b0e84[ at ]b41g2000pra.googlegrou= ps.com</FONT></A><FONT=20 face=3DArial size=3D2>...<BR>>>>>=20 Rob;<BR>>>>><BR>>>>> Maybe if you knew how to = work the=20 worlds most popular database, then<BR>>>>> maybe- just = maybe- you=20 wouldn't be stuck wiht a paperweight-sized<BR>>>>>=20 database<BR>>>>><BR>>>>><BR>>>>><BR>&= gt;>>><BR>>>>><BR>>>>><BR>>>>&g= t;=20 On Dec 29, 9:50 pm, Robert Morley <</FONT><A=20 href=3D"mailto:rmor...[ at ]N0.Freak1n.sparn.magma.ca"><FONT face=3DArial=20 size=3D2>rmor...[ at ]N0.Freak1n.sparn.magma.ca</FONT></A><FONT face=3DArial=20 size=3D2>><BR>>>>> wrote:<BR>>>>>> Tony = Toews [MVP]=20 wrote:<BR>>>>>> > "Andy" <</FONT><A=20 href=3D"mailto:DontW...[ at ]email.com"><FONT face=3DArial=20 size=3D2>DontW...[ at ]email.com</FONT></A><FONT face=3DArial size=3D2>>=20 wrote:<BR>>>>>><BR>>>>>> > Please = ignore Aaron=20 Kempf's posting as he responds with SQL Server <BR>>>>>> = >=20 and<BR>>>>>> > ADPs as the answer even when that would = have no=20 resemblance to the<BR>>>>>> >=20 problem.<BR>>>>>><BR>>>>>> >=20 Tony<BR>>>>>><BR>>>>>> What's funny about = this is=20 that in the case I spoke of, I was using an <BR>>>>>>=20 A2K<BR>>>>>> ADP.=20 ;)<BR>>>>>><BR>>>>>>=20 Rob<BR>>>>><BR>>>>><BR>>>><BR>>>&g= t;<BR>>><BR>>><BR>><BR>>=20 <BR><BR></FONT></DIV></BODY></HTML> ------=_NextPart_000_0024_01C96B3D.A67D5AE0--

Re: A2K Runtime Crashes on DoCmd.Quit "Gina Whipp" <NotInterested[ at ]InViruses.com> 12/31/2008 4:54:34 PM 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" <DontWant[ at ]email.com> wrote in message news:urJ3Re2aJHA.4068[ at ]TK2MSFTNGP06.phx.gbl... 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" <NotInterested[ at ]InViruses.com> wrote in message news:eYHezztaJHA.2640[ at ]TK2MSFTNGP03.phx.gbl... [Quoted Text] > 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" <DontWant[ at ]email.com> wrote in message > news:uGDHastaJHA.1676[ at ]TK2MSFTNGP03.phx.gbl... >> 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" <NotInterested[ at ]InViruses.com> wrote in message >> news:%23rLzFbpaJHA.1704[ at ]TK2MSFTNGP05.phx.gbl... >>> 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" <DontWant[ at ]email.com> wrote in message >>> news:ONsTFTpaJHA.4504[ at ]TK2MSFTNGP04.phx.gbl... >>>> 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 [ at ] g m a i l . c o m" <aaron.kempf[ at ]gmail.com> >>>> wrote in message >>>> news:52cc81fc-1c5c-4ec6-abab-e0caf87b0e84[ at ]b41g2000pra.googlegroups.com... >>>> 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 <rmor...[ at ]N0.Freak1n.sparn.magma.ca> >>>> wrote: >>>>> Tony Toews [MVP] wrote: >>>>> > "Andy" <DontW...[ at ]email.com> 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 >>>> >>>> >>> >>> >> >> > >

Re: A2K Runtime Crashes on DoCmd.Quit "Andy" <DontWant[ at ]email.com> 12/31/2008 6:00:48 PM 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" <NotInterested[ at ]InViruses.com> wrote in message news:eI$X3h2aJHA.5976[ at ]TK2MSFTNGP03.phx.gbl... [Quoted Text] > 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" <DontWant[ at ]email.com> wrote in message > news:urJ3Re2aJHA.4068[ at ]TK2MSFTNGP06.phx.gbl... > 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" <NotInterested[ at ]InViruses.com> wrote in message > news:eYHezztaJHA.2640[ at ]TK2MSFTNGP03.phx.gbl... >> 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" <DontWant[ at ]email.com> wrote in message >> news:uGDHastaJHA.1676[ at ]TK2MSFTNGP03.phx.gbl... >>> 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" <NotInterested[ at ]InViruses.com> wrote in message >>> news:%23rLzFbpaJHA.1704[ at ]TK2MSFTNGP05.phx.gbl... >>>> 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" <DontWant[ at ]email.com> wrote in message >>>> news:ONsTFTpaJHA.4504[ at ]TK2MSFTNGP04.phx.gbl... >>>>> 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 [ at ] g m a i l . c o m" <aaron.kempf[ at ]gmail.com> >>>>> wrote in message >>>>> news:52cc81fc-1c5c-4ec6-abab-e0caf87b0e84[ at ]b41g2000pra.googlegroups.com... >>>>> 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 <rmor...[ at ]N0.Freak1n.sparn.magma.ca> >>>>> wrote: >>>>>> Tony Toews [MVP] wrote: >>>>>> > "Andy" <DontW...[ at ]email.com> 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 >>>>> >>>>> >>>> >>>> >>> >>> >> >> > > >

Re: A2K Runtime Crashes on DoCmd.Quit "Andy" <DontWant[ at ]email.com> 12/31/2008 6:04:52 PM Note: Microsoft ActiveX Data Objects 2.8 Library was originally Microsoft ActiveX Data Objects 2.1 Library. "Andy" <DontWant[ at ]email.com> wrote in message news:%23V3J5G3aJHA.4068[ at ]TK2MSFTNGP06.phx.gbl... [Quoted Text] > > 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" <NotInterested[ at ]InViruses.com> wrote in message > news:eI$X3h2aJHA.5976[ at ]TK2MSFTNGP03.phx.gbl... >> 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" <DontWant[ at ]email.com> wrote in message >> news:urJ3Re2aJHA.4068[ at ]TK2MSFTNGP06.phx.gbl... >> 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" <NotInterested[ at ]InViruses.com> wrote in message >> news:eYHezztaJHA.2640[ at ]TK2MSFTNGP03.phx.gbl... >>> 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" <DontWant[ at ]email.com> wrote in message >>> news:uGDHastaJHA.1676[ at ]TK2MSFTNGP03.phx.gbl... >>>> 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" <NotInterested[ at ]InViruses.com> wrote in message >>>> news:%23rLzFbpaJHA.1704[ at ]TK2MSFTNGP05.phx.gbl... >>>>> 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" <DontWant[ at ]email.com> wrote in message >>>>> news:ONsTFTpaJHA.4504[ at ]TK2MSFTNGP04.phx.gbl... >>>>>> 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 [ at ] g m a i l . c o m" <aaron.kempf[ at ]gmail.com> >>>>>> wrote in message >>>>>> news:52cc81fc-1c5c-4ec6-abab-e0caf87b0e84[ at ]b41g2000pra.googlegroups.com... >>>>>> 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 <rmor...[ at ]N0.Freak1n.sparn.magma.ca> >>>>>> wrote: >>>>>>> Tony Toews [MVP] wrote: >>>>>>> > "Andy" <DontW...[ at ]email.com> 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 >>>>>> >>>>>> >>>>> >>>>> >>>> >>>> >>> >>> >> >> >> > >

Re: A2K Runtime Crashes on DoCmd.Quit "Gina Whipp" <NotInterested[ at ]InViruses.com> 12/31/2008 6:12:17 PM 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" <DontWant[ at ]email.com> wrote in message news:%23V3J5G3aJHA.4068[ at ]TK2MSFTNGP06.phx.gbl... [Quoted Text] > > 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" <NotInterested[ at ]InViruses.com> wrote in message > news:eI$X3h2aJHA.5976[ at ]TK2MSFTNGP03.phx.gbl... >> 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" <DontWant[ at ]email.com> wrote in message >> news:urJ3Re2aJHA.4068[ at ]TK2MSFTNGP06.phx.gbl... >> 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" <NotInterested[ at ]InViruses.com> wrote in message >> news:eYHezztaJHA.2640[ at ]TK2MSFTNGP03.phx.gbl... >>> 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" <DontWant[ at ]email.com> wrote in message >>> news:uGDHastaJHA.1676[ at ]TK2MSFTNGP03.phx.gbl... >>>> 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" <NotInterested[ at ]InViruses.com> wrote in message >>>> news:%23rLzFbpaJHA.1704[ at ]TK2MSFTNGP05.phx.gbl... >>>>> 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" <DontWant[ at ]email.com> wrote in message >>>>> news:ONsTFTpaJHA.4504[ at ]TK2MSFTNGP04.phx.gbl... >>>>>> 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 [ at ] g m a i l . c o m" <aaron.kempf[ at ]gmail.com> >>>>>> wrote in message >>>>>> news:52cc81fc-1c5c-4ec6-abab-e0caf87b0e84[ at ]b41g2000pra.googlegroups.com... >>>>>> 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 <rmor...[ at ]N0.Freak1n.sparn.magma.ca> >>>>>> wrote: >>>>>>> Tony Toews [MVP] wrote: >>>>>>> > "Andy" <DontW...[ at ]email.com> 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 >>>>>> >>>>>> >>>>> >>>>> >>>> >>>> >>> >>> >> >> >> > >

Re: A2K Runtime Crashes on DoCmd.Quit "Gina Whipp" <NotInterested[ at ]InViruses.com> 12/31/2008 6:12:57 PM 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 "Andy" <DontWant[ at ]email.com> wrote in message news:OlWWKJ3aJHA.1528[ at ]TK2MSFTNGP03.phx.gbl... [Quoted Text] > Note: Microsoft ActiveX Data Objects 2.8 Library was originally Microsoft > ActiveX Data Objects 2.1 Library. > > > "Andy" <DontWant[ at ]email.com> wrote in message > news:%23V3J5G3aJHA.4068[ at ]TK2MSFTNGP06.phx.gbl... >> >> 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" <NotInterested[ at ]InViruses.com> wrote in message >> news:eI$X3h2aJHA.5976[ at ]TK2MSFTNGP03.phx.gbl... >>> 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" <DontWant[ at ]email.com> wrote in message >>> news:urJ3Re2aJHA.4068[ at ]TK2MSFTNGP06.phx.gbl... >>> 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" <NotInterested[ at ]InViruses.com> wrote in message >>> news:eYHezztaJHA.2640[ at ]TK2MSFTNGP03.phx.gbl... >>>> 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" <DontWant[ at ]email.com> wrote in message >>>> news:uGDHastaJHA.1676[ at ]TK2MSFTNGP03.phx.gbl... >>>>> 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" <NotInterested[ at ]InViruses.com> wrote in message >>>>> news:%23rLzFbpaJHA.1704[ at ]TK2MSFTNGP05.phx.gbl... >>>>>> 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" <DontWant[ at ]email.com> wrote in message >>>>>> news:ONsTFTpaJHA.4504[ at ]TK2MSFTNGP04.phx.gbl... >>>>>>> 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 [ at ] g m a i l . c o m" <aaron.kempf[ at ]gmail.com> >>>>>>> wrote in message >>>>>>> news:52cc81fc-1c5c-4ec6-abab-e0caf87b0e84[ at ]b41g2000pra.googlegroups.com... >>>>>>> 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 >>>>>>> <rmor...[ at ]N0.Freak1n.sparn.magma.ca> >>>>>>> wrote: >>>>>>>> Tony Toews [MVP] wrote: >>>>>>>> > "Andy" <DontW...[ at ]email.com> 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 >>>>>>> >>>>>>> >>>>>> >>>>>> >>>>> >>>>> >>>> >>>> >>> >>> >>> >> >> > >

Re: A2K Runtime Crashes on DoCmd.Quit "Gina Whipp" <NotInterested[ at ]InViruses.com> 12/31/2008 6:24:07 PM 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 "Andy" <DontWant[ at ]email.com> wrote in message news:OlWWKJ3aJHA.1528[ at ]TK2MSFTNGP03.phx.gbl... [Quoted Text] > Note: Microsoft ActiveX Data Objects 2.8 Library was originally Microsoft > ActiveX Data Objects 2.1 Library. > > > "Andy" <DontWant[ at ]email.com> wrote in message > news:%23V3J5G3aJHA.4068[ at ]TK2MSFTNGP06.phx.gbl... >> >> 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" <NotInterested[ at ]InViruses.com> wrote in message >> news:eI$X3h2aJHA.5976[ at ]TK2MSFTNGP03.phx.gbl... >>> 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" <DontWant[ at ]email.com> wrote in message >>> news:urJ3Re2aJHA.4068[ at ]TK2MSFTNGP06.phx.gbl... >>> 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" <NotInterested[ at ]InViruses.com> wrote in message >>> news:eYHezztaJHA.2640[ at ]TK2MSFTNGP03.phx.gbl... >>>> 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" <DontWant[ at ]email.com> wrote in message >>>> news:uGDHastaJHA.1676[ at ]TK2MSFTNGP03.phx.gbl... >>>>> 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" <NotInterested[ at ]InViruses.com> wrote in message >>>>> news:%23rLzFbpaJHA.1704[ at ]TK2MSFTNGP05.phx.gbl... >>>>>> 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" <DontWant[ at ]email.com> wrote in message >>>>>> news:ONsTFTpaJHA.4504[ at ]TK2MSFTNGP04.phx.gbl... >>>>>>> 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 [ at ] g m a i l . c o m" <aaron.kempf[ at ]gmail.com> >>>>>>> wrote in message >>>>>>> news:52cc81fc-1c5c-4ec6-abab-e0caf87b0e84[ at ]b41g2000pra.googlegroups.com... >>>>>>> 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 >>>>>>> <rmor...[ at ]N0.Freak1n.sparn.magma.ca> >>>>>>> wrote: >>>>>>>> Tony Toews [MVP] wrote: >>>>>>>> > "Andy" <DontW...[ at ]email.com> 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 >>>>>>> >>>>>>> >>>>>> >>>>>> >>>>> >>>>> >>>> >>>> >>> >>> >>> >> >> > >

Re: A2K Runtime Crashes on DoCmd.Quit "Andy" <DontWant[ at ]email.com> 12/31/2008 6:24:40 PM 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" <NotInterested[ at ]InViruses.com> wrote in message news:%23aPmSN3aJHA.3952[ at ]TK2MSFTNGP05.phx.gbl... [Quoted Text] > 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" <DontWant[ at ]email.com> wrote in message > news:%23V3J5G3aJHA.4068[ at ]TK2MSFTNGP06.phx.gbl... >> >> 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" <NotInterested[ at ]InViruses.com> wrote in message >> news:eI$X3h2aJHA.5976[ at ]TK2MSFTNGP03.phx.gbl... >>> 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" <DontWant[ at ]email.com> wrote in message >>> news:urJ3Re2aJHA.4068[ at ]TK2MSFTNGP06.phx.gbl... >>> 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" <NotInterested[ at ]InViruses.com> wrote in message >>> news:eYHezztaJHA.2640[ at ]TK2MSFTNGP03.phx.gbl... >>>> 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" <DontWant[ at ]email.com> wrote in message >>>> news:uGDHastaJHA.1676[ at ]TK2MSFTNGP03.phx.gbl... >>>>> 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" <NotInterested[ at ]InViruses.com> wrote in message >>>>> news:%23rLzFbpaJHA.1704[ at ]TK2MSFTNGP05.phx.gbl... >>>>>> 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" <DontWant[ at ]email.com> wrote in message >>>>>> news:ONsTFTpaJHA.4504[ at ]TK2MSFTNGP04.phx.gbl... >>>>>>> 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 [ at ] g m a i l . c o m" <aaron.kempf[ at ]gmail.com> >>>>>>> wrote in message >>>>>>> news:52cc81fc-1c5c-4ec6-abab-e0caf87b0e84[ at ]b41g2000pra.googlegroups.com... >>>>>>> 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 >>>>>>> <rmor...[ at ]N0.Freak1n.sparn.magma.ca> >>>>>>> wrote: >>>>>>>> Tony Toews [MVP] wrote: >>>>>>>> > "Andy" <DontW...[ at ]email.com> 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 >>>>>>> >>>>>>> >>>>>> >>>>>> >>>>> >>>>> >>>> >>>> >>> >>> >>> >> >> > >

Re: A2K Runtime Crashes on DoCmd.Quit "Gina Whipp" <NotInterested[ at ]InViruses.com> 12/31/2008 6:34:29 PM 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" <DontWant[ at ]email.com> wrote in message news:uUHTOU3aJHA.1600[ at ]TK2MSFTNGP04.phx.gbl... [Quoted Text] > 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" <NotInterested[ at ]InViruses.com> wrote in message > news:%23aPmSN3aJHA.3952[ at ]TK2MSFTNGP05.phx.gbl... >> 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" <DontWant[ at ]email.com> wrote in message >> news:%23V3J5G3aJHA.4068[ at ]TK2MSFTNGP06.phx.gbl... >>> >>> 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" <NotInterested[ at ]InViruses.com> wrote in message >>> news:eI$X3h2aJHA.5976[ at ]TK2MSFTNGP03.phx.gbl... >>>> 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" <DontWant[ at ]email.com> wrote in message >>>> news:urJ3Re2aJHA.4068[ at ]TK2MSFTNGP06.phx.gbl... >>>> 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" <NotInterested[ at ]InViruses.com> wrote in message >>>> news:eYHezztaJHA.2640[ at ]TK2MSFTNGP03.phx.gbl... >>>>> 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" <DontWant[ at ]email.com> wrote in message >>>>> news:uGDHastaJHA.1676[ at ]TK2MSFTNGP03.phx.gbl... >>>>>> 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" <NotInterested[ at ]InViruses.com> wrote in message >>>>>> news:%23rLzFbpaJHA.1704[ at ]TK2MSFTNGP05.phx.gbl... >>>>>>> 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" <DontWant[ at ]email.com> wrote in message >>>>>>> news:ONsTFTpaJHA.4504[ at ]TK2MSFTNGP04.phx.gbl... >>>>>>>> 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 [ at ] g m a i l . c o m" <aaron.kempf[ at ]gmail.com> >>>>>>>> wrote in message >>>>>>>> news:52cc81fc-1c5c-4ec6-abab-e0caf87b0e84[ at ]b41g2000pra.googlegroups.com... >>>>>>>> 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 >>>>>>>> <rmor...[ at ]N0.Freak1n.sparn.magma.ca> >>>>>>>> wrote: >>>>>>>>> Tony Toews [MVP] wrote: >>>>>>>>> > "Andy" <DontW...[ at ]email.com> 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 >>>>>>>> >>>>>>>> >>>>>>> >>>>>>> >>>>>> >>>>>> >>>>> >>>>> >>>> >>>> >>>> >>> >>> >> >> > >

Re: A2K Runtime Crashes on DoCmd.Quit "Gina Whipp" <NotInterested[ at ]InViruses.com> 12/31/2008 6:44:04 PM 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" <DontWant[ at ]email.com> wrote in message news:ONsTFTpaJHA.4504[ at ]TK2MSFTNGP04.phx.gbl... [Quoted Text] > 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 [ at ] g m a i l . c o m" <aaron.kempf[ at ]gmail.com> wrote > in message > news:52cc81fc-1c5c-4ec6-abab-e0caf87b0e84[ at ]b41g2000pra.googlegroups.com... > 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 <rmor...[ at ]N0.Freak1n.sparn.magma.ca> > wrote: >> Tony Toews [MVP] wrote: >> > "Andy" <DontW...[ at ]email.com> 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 > >

Re: A2K Runtime Crashes on DoCmd.Quit "Andy" <DontWant[ at ]email.com> 12/31/2008 6:56:06 PM 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" <NotInterested[ at ]InViruses.com> wrote in message news:uwfjsZ3aJHA.4684[ at ]TK2MSFTNGP03.phx.gbl... [Quoted Text] > 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" <DontWant[ at ]email.com> wrote in message > news:uUHTOU3aJHA.1600[ at ]TK2MSFTNGP04.phx.gbl... >> 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" <NotInterested[ at ]InViruses.com> wrote in message >> news:%23aPmSN3aJHA.3952[ at ]TK2MSFTNGP05.phx.gbl... >>> 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" <DontWant[ at ]email.com> wrote in message >>> news:%23V3J5G3aJHA.4068[ at ]TK2MSFTNGP06.phx.gbl... >>>> >>>> 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" <NotInterested[ at ]InViruses.com> wrote in message >>>> news:eI$X3h2aJHA.5976[ at ]TK2MSFTNGP03.phx.gbl... >>>>> 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" <DontWant[ at ]email.com> wrote in message >>>>> news:urJ3Re2aJHA.4068[ at ]TK2MSFTNGP06.phx.gbl... >>>>> 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" <NotInterested[ at ]InViruses.com> wrote in message >>>>> news:eYHezztaJHA.2640[ at ]TK2MSFTNGP03.phx.gbl... >>>>>> 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" <DontWant[ at ]email.com> wrote in message >>>>>> news:uGDHastaJHA.1676[ at ]TK2MSFTNGP03.phx.gbl... >>>>>>> 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" <NotInterested[ at ]InViruses.com> wrote in message >>>>>>> news:%23rLzFbpaJHA.1704[ at ]TK2MSFTNGP05.phx.gbl... >>>>>>>> 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" <DontWant[ at ]email.com> wrote in message >>>>>>>> news:ONsTFTpaJHA.4504[ at ]TK2MSFTNGP04.phx.gbl... >>>>>>>>> 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 [ at ] g m a i l . c o m" >>>>>>>>> <aaron.kempf[ at ]gmail.com> >>>>>>>>> wrote in message >>>>>>>>> news:52cc81fc-1c5c-4ec6-abab-e0caf87b0e84[ at ]b41g2000pra.googlegroups.com... >>>>>>>>> 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 >>>>>>>>> <rmor...[ at ]N0.Freak1n.sparn.magma.ca> >>>>>>>>> wrote: >>>>>>>>>> Tony Toews [MVP] wrote: >>>>>>>>>> > "Andy" <DontW...[ at ]email.com> 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 >>>>>>>>> >>>>>>>>> >>>>>>>> >>>>>>>> >>>>>>> >>>>>>> >>>>>> >>>>>> >>>>> >>>>> >>>>> >>>> >>>> >>> >>> >> >> > >

Re: A2K Runtime Crashes on DoCmd.Quit "Andy" <DontWant[ at ]email.com> 12/31/2008 7:03:51 PM Gina; Already using that code. It doesn't generate an Error Message. Just gets a RunTime Crash. "Gina Whipp" <NotInterested[ at ]InViruses.com> wrote in message news:ORRXDf3aJHA.4488[ at ]TK2MSFTNGP06.phx.gbl... [Quoted Text] > 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" <DontWant[ at ]email.com> wrote in message > news:ONsTFTpaJHA.4504[ at ]TK2MSFTNGP04.phx.gbl... >> 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 [ at ] g m a i l . c o m" <aaron.kempf[ at ]gmail.com> wrote >> in message >> news:52cc81fc-1c5c-4ec6-abab-e0caf87b0e84[ at ]b41g2000pra.googlegroups.com... >> 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 <rmor...[ at ]N0.Freak1n.sparn.magma.ca> >> wrote: >>> Tony Toews [MVP] wrote: >>> > "Andy" <DontW...[ at ]email.com> 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 >> >> > >

Re: A2K Runtime Crashes on DoCmd.Quit "Gina Whipp" <NotInterested[ at ]InViruses.com> 12/31/2008 10:02:56 PM 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 "Andy" <DontWant[ at ]email.com> wrote in message news:etuuyl3aJHA.1676[ at ]TK2MSFTNGP03.phx.gbl... [Quoted Text] > 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" <NotInterested[ at ]InViruses.com> wrote in message > news:uwfjsZ3aJHA.4684[ at ]TK2MSFTNGP03.phx.gbl... >> 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" <DontWant[ at ]email.com> wrote in message >> news:uUHTOU3aJHA.1600[ at ]TK2MSFTNGP04.phx.gbl... >>> 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" <NotInterested[ at ]InViruses.com> wrote in message >>> news:%23aPmSN3aJHA.3952[ at ]TK2MSFTNGP05.phx.gbl... >>>> 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" <DontWant[ at ]email.com> wrote in message >>>> news:%23V3J5G3aJHA.4068[ at ]TK2MSFTNGP06.phx.gbl... >>>>> >>>>> 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" <NotInterested[ at ]InViruses.com> wrote in message >>>>> news:eI$X3h2aJHA.5976[ at ]TK2MSFTNGP03.phx.gbl... >>>>>> 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" <DontWant[ at ]email.com> wrote in message >>>>>> news:urJ3Re2aJHA.4068[ at ]TK2MSFTNGP06.phx.gbl... >>>>>> 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" <NotInterested[ at ]InViruses.com> wrote in message >>>>>> news:eYHezztaJHA.2640[ at ]TK2MSFTNGP03.phx.gbl... >>>>>>> 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" <DontWant[ at ]email.com> wrote in message >>>>>>> news:uGDHastaJHA.1676[ at ]TK2MSFTNGP03.phx.gbl... >>>>>>>> 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" <NotInterested[ at ]InViruses.com> wrote in message >>>>>>>> news:%23rLzFbpaJHA.1704[ at ]TK2MSFTNGP05.phx.gbl... >>>>>>>>> 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" <DontWant[ at ]email.com> wrote in message >>>>>>>>> news:ONsTFTpaJHA.4504[ at ]TK2MSFTNGP04.phx.gbl... >>>>>>>>>> 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 [ at ] g m a i l . c o m" >>>>>>>>>> <aaron.kempf[ at ]gmail.com> >>>>>>>>>> wrote in message >>>>>>>>>> news:52cc81fc-1c5c-4ec6-abab-e0caf87b0e84[ at ]b41g2000pra.googlegroups.com... >>>>>>>>>> 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 >>>>>>>>>> <rmor...[ at ]N0.Freak1n.sparn.magma.ca> >>>>>>>>>> wrote: >>>>>>>>>>> Tony Toews [MVP] wrote: >>>>>>>>>>> > "Andy" <DontW...[ at ]email.com> 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 >>>>>>>>>> >>>>>>>>>> >>>>>>>>> >>>>>>>>> >>>>>>>> >>>>>>>> >>>>>>> >>>>>>> >>>>>> >>>>>> >>>>>> >>>>> >>>>> >>>> >>>> >>> >>> >> >> > >

Re: A2K Runtime Crashes on DoCmd.Quit "Tony Toews [MVP]" <ttoews[ at ]telusplanet.net> 1/1/2009 1:14:35 AM "Andy" <DontWant[ at ]email.com> wrote: [Quoted Text] >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/