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 |
#16
|
|||
|
|||
A2K Runtime Crashes on DoCmd.Quit
Andy,
Just had a thought... I wonder on the new machines is it 64 bit and the older machines 32 bit? -- Gina Whipp "I feel I have been denied critical, need to know, information!" - Tremors II "Andy" wrote in message ... Tony; Thank You again for replying. global variables... Recordset. Do remember somewhere along the line getting the same type of crash w/ Recordset.Requery. Not the case in this situation. Also not sure I understand "global variables". Searched Help for "global variables" and "set global variables". Nothing obvious that would pertain to this. Will remove VBA for Extensibility. Tony; think we're on the wrong path. We have a existing Install CD. The same CD that installed this application including "ART" successfully twice before. Once shortly after the computer was purchased. Once again when the machine had to be "Rebuilt" about a year and a half ago. This time the app starts and gets a Run-Time crash at a fundamental command: DoCmd.Quit. Thinking something changed with the machine. Microsoft has brought out a lot of patches for Windows XP in a year and a half and ART has been updated. In the early 1990s a local company was selling a DOS based DBASE Program. Friends with the owners of 3 companies that bought it. I was able to bring it Forward all the way to early Windows XP machines. Each time a new computer was needed the DOS program was copied onto the H/Drive and it ran. Then on the last 2 new computers, (1-Dell, 1-H/P) the program won't even open. When the Shortcut Icon is dbl-clicked to start the program all You see on the screen is a "Blink" and the program closes. Set the "Compatibility" options for the shortcut and still the same thing. Called Dell and H/P. Got the "It isn't our program" answer. In both cases don't think its the program. Think an update to Windows changed "Something". Same CD. Same Install. Your thoughts? Andy "Tony Toews [MVP]" wrote in message ... "Andy" wrote: At first the full code (Included Below) wasn't included because I didn't want to make You kind people read a lot of redundancies. The Error Traps have been in place since the app was originally created. Each trap does 2 things. Shows the Access Internal Error msg and displays the name of the Command that failed. Neither displays any message. All that shows is: "Execution of this application has stopped due to a run-time error." "The application can't continue and will be shut down." Then I'm not sure. Is there some code that sets global variables such as a database or recordset or some such on startup? "I've remove the last reference, VBA for Extensibility.. It's automatically inserted by Access when you convert a database to a newer version. Although that could've been from A97 to A2000 or something like that. IOW quite a while ago." The application was started and completed in Office Developer 2000 using Access 2000. So it has never been brought forward from an older version of Access. We did re-install the app once before on the same computer. The machine was "Rebuilt" from scratch about a year ago. Fair enough. But have you tried removing that reference anyhow? Tony, one last thing. What is "IOW"? In Other Words. Andy Full Code for both Commands in frmLogin Private Sub cmdExit_Click() On Error GoTo Err_cmdExit_Click Dim Msg, Style, Title, Help, Ctxt Those Dims are automatically Variant type of fields not that that should make a difference in this problem. Msg = MsgBox("Either:" & vbCrLf & Error$ & vbCrLf & vbCrLf & _ "Or this command ''cmdExit_Click'' doesn't understand Your input. " & vbCrLf & _ " Click the OK button" & vbCrLf & _ " Try the steps again." & vbCrLf & _ " If You Need Help, click the OK button then press the F1 key.", vbOKOnly + vbCritical, "OurCompany") For now just comment the above lines and put in msgbox Err.description and see what happens. 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/ |
Thread Tools | |
Display Modes | |
|
|