View Single Post
  #40  
Old February 15th, 2009, 05:53 AM posted to microsoft.public.access.forms,microsoft.public.access,microsoft.public.access.modulescoding
Jack Cannon
external usenet poster
 
Posts: 151
Default A2K Runtime Crashes on DoCmd.Quit

Andy,

I also experienced problems with Access 2000 crashing with no apparent
reason and in conditions that were totally illogical. That did not happen
after upgrading to 2002. A common factor with the 2000 crashes was that it
appeared to start happening when the file reached a certain critical size
(after compacting and repairing). That size was about 10K. Whether the size
or even the version was a factor is unknown. I can only say with confidence
that the problem did go away after the upgrade to 2002.

Jack Cannon

"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