If this is your first visit, be sure to check out the FAQ by clicking the link above. You may have to register before you can post: click the register link above to proceed. To start viewing messages, select the forum that you want to visit from the selection below. |
|
|
Thread Tools | Display Modes |
#1
|
|||
|
|||
A2K Runtime Crashes on DoCmd.Quit
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 |
#2
|
|||
|
|||
A2K Runtime Crashes on DoCmd.Quit
Andy wrote:
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 |
#3
|
|||
|
|||
A2K Runtime Crashes on DoCmd.Quit
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" wrote: 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 |
#4
|
|||
|
|||
A2K Runtime Crashes on DoCmd.Quit
"Andy" wrote:
Please ignore Aaron Kempf's posting as he responds with SQL Server and ADPs as the answer even when that would have no resemblance to the problem. Tony -- 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/ |
#5
|
|||
|
|||
A2K Runtime Crashes on DoCmd.Quit
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/libr...70(VS.80).aspx ---------------------------------------------------------------------------------------- On Dec 26, 7:51*pm, "Tony Toews [MVP]" wrote: "Andy" wrote: Please ignore Aaron Kempf's posting as he responds with SQL Server and ADPs as the answer even when that would have no resemblance to the problem. Tony -- 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/ |
#6
|
|||
|
|||
A2K Runtime Crashes on DoCmd.Quit
Tony Toews [MVP] wrote:
"Andy" wrote: Please ignore Aaron Kempf's posting as he responds with SQL Server and ADPs as the answer even when that would have no resemblance to the problem. Tony What's funny about this is that in the case I spoke of, I was using an A2K ADP. Rob |
#7
|
|||
|
|||
A2K Runtime Crashes on DoCmd.Quit
Rob;
Maybe if you knew how to work the worlds most popular database, then maybe- just maybe- you wouldn't be stuck wiht a paperweight-sized database On Dec 29, 9:50*pm, Robert Morley wrote: Tony Toews [MVP] wrote: "Andy" wrote: Please ignore Aaron Kempf's posting as he responds with SQL Server and ADPs as the answer even when that would have no resemblance to the problem. Tony What's funny about this is that in the case I spoke of, I was using an A2K ADP. Rob |
#8
|
|||
|
|||
A2K Runtime Crashes on DoCmd.Quit
Gentlemen;
Thank You all for reading and replying to my post. Created this mdb front end and mde back using Office 2000 Developer. Its not that Dbase doesn't run At All. It does run on other machines, (all Stand Alones). The Crash happens at the "Log In" frm. No matter if the User clicks "Continue" or the cmdExit OnClick Event is: Private Sub cmdExit_Click() DoCmd.Quit End Sub Access Crashes due to a RunTime Error. Why? How do I discover what is crashing? What is causing it? Again Thank You for taking the time to read and reply to my post. Andy "a a r o n . k e m p f @ g m a i l . c o m" wrote in message ... Rob; Maybe if you knew how to work the worlds most popular database, then maybe- just maybe- you wouldn't be stuck wiht a paperweight-sized database On Dec 29, 9:50 pm, Robert Morley wrote: Tony Toews [MVP] wrote: "Andy" wrote: Please ignore Aaron Kempf's posting as he responds with SQL Server and ADPs as the answer even when that would have no resemblance to the problem. Tony What's funny about this is that in the case I spoke of, I was using an A2K ADP. Rob |
#9
|
|||
|
|||
A2K Runtime Crashes on DoCmd.Quit
Andy,
Are you saying that when not on stand alone machines everyone is accessing the same front end? I think more details are going to be needed to figure out exactly what your issue is. -- Gina Whipp "I feel I have been denied critical, need to know, information!" - Tremors II "Andy" wrote in message ... Gentlemen; Thank You all for reading and replying to my post. Created this mdb front end and mde back using Office 2000 Developer. Its not that Dbase doesn't run At All. It does run on other machines, (all Stand Alones). The Crash happens at the "Log In" frm. No matter if the User clicks "Continue" or the cmdExit OnClick Event is: Private Sub cmdExit_Click() DoCmd.Quit End Sub Access Crashes due to a RunTime Error. Why? How do I discover what is crashing? What is causing it? Again Thank You for taking the time to read and reply to my post. Andy "a a r o n . k e m p f @ g m a i l . c o m" wrote in message ... Rob; Maybe if you knew how to work the worlds most popular database, then maybe- just maybe- you wouldn't be stuck wiht a paperweight-sized database On Dec 29, 9:50 pm, Robert Morley wrote: Tony Toews [MVP] wrote: "Andy" wrote: Please ignore Aaron Kempf's posting as he responds with SQL Server and ADPs as the answer even when that would have no resemblance to the problem. Tony What's funny about this is that in the case I spoke of, I was using an A2K ADP. Rob |
#10
|
|||
|
|||
A2K Runtime Crashes on DoCmd.Quit
Gina;
Thank You for reading and replying to my post. What I mean is that I have installed the app on other computers to test the installation. All of those machines are stand alones as is the computer that is getting the Runtime crash. The computer that the app has been running on for years crashed out and Windows needed to be re-installed from scratch. Now, using the same install CD and the Same FE (MDB) and BE (MDE) we are getting Runtime crashes no matter if we click on cmdContinue to open another frm or to simply click Exit to shut the app down. Andy "Gina Whipp" wrote in message ... Andy, Are you saying that when not on stand alone machines everyone is accessing the same front end? I think more details are going to be needed to figure out exactly what your issue is. -- Gina Whipp "I feel I have been denied critical, need to know, information!" - Tremors II "Andy" wrote in message ... Gentlemen; Thank You all for reading and replying to my post. Created this mdb front end and mde back using Office 2000 Developer. Its not that Dbase doesn't run At All. It does run on other machines, (all Stand Alones). The Crash happens at the "Log In" frm. No matter if the User clicks "Continue" or the cmdExit OnClick Event is: Private Sub cmdExit_Click() DoCmd.Quit End Sub Access Crashes due to a RunTime Error. Why? How do I discover what is crashing? What is causing it? Again Thank You for taking the time to read and reply to my post. Andy "a a r o n . k e m p f @ g m a i l . c o m" wrote in message ... Rob; Maybe if you knew how to work the worlds most popular database, then maybe- just maybe- you wouldn't be stuck wiht a paperweight-sized database On Dec 29, 9:50 pm, Robert Morley wrote: Tony Toews [MVP] wrote: "Andy" wrote: Please ignore Aaron Kempf's posting as he responds with SQL Server and ADPs as the answer even when that would have no resemblance to the problem. Tony What's funny about this is that in the case I spoke of, I was using an A2K ADP. Rob |
Thread Tools | |
Display Modes | |
|
|