Has anyone had any issues where Access shutsdown on the execution of a Command Button or on a print report command from the file menu? If so what is this all about? I have had this problem a few times, and I can't determine a definate pattern. If I check the system log files, I find a physical memory dump consistant with the shutdown. Any ideas on this? I need to resolve this ASAP. It also occurs on other CPUs that access the database from the server. Thanks.
Tek-Tips is the largest IT community on the Internet today!
Members share and learn making Tek-Tips Forums the best source of peer-reviewed technical information on the Internet!
-
Congratulations Wanet Telecoms Ltd on being selected by the Tek-Tips community for having the most helpful posts in the forums last week. Way to Go!
CPU Shutdown 1
- Thread starter Channah
- Start date
-
1
- #2
Might be one of the fixes addressed @:
- Thread starter
- #4
Sean, All of the users that access this application have individual licences on their own PCs. Access is not on the server, they are just hitting the application that lives in a folder on the server. Therein may be my problem. My only concern is that it doesn't happen all the time. It is an occasional problem...
- Thread starter
- #6
Thanks... but lets spare everyone the Windows jokes and see if we can find a real solution here... here is what I have gathered from a bluescreen from a co-workers CPU...
MS access has caused a page fault in non pageable area...
does this help out any? I am still searching for clues here.
MS access has caused a page fault in non pageable area...
does this help out any? I am still searching for clues here.
If you don't have error handling built into the routine, and the user doesn't have permission to modify the code, the application may shut down. I've seen that a couple of times in Access 97.
Since I've had this happen, I usually try to have some kind of error handling in my routines, even if it's only "Exit Sub".
Since I've had this happen, I usually try to have some kind of error handling in my routines, even if it's only "Exit Sub".
- Thread starter
- #8
Here is the code that lives behind each of the Cmd buttons...
Private Sub cmdIssuesRpt_Click()
On Error GoTo Err_cmdIssuesRpt_Click
Dim stDocName As String
stDocName = "Unsettled Issues"
DoCmd.OpenReport stDocName, acPreview
Exit_cmdIssuesRpt_Click:
Exit Sub
Err_cmdIssuesRpt_Click:
MsgBox Err.Description
Resume Exit_cmdIssuesRpt_Click
End Sub
Do I have it right or have I goofed it up somewhere?
Private Sub cmdIssuesRpt_Click()
On Error GoTo Err_cmdIssuesRpt_Click
Dim stDocName As String
stDocName = "Unsettled Issues"
DoCmd.OpenReport stDocName, acPreview
Exit_cmdIssuesRpt_Click:
Exit Sub
Err_cmdIssuesRpt_Click:
MsgBox Err.Description
Resume Exit_cmdIssuesRpt_Click
End Sub
Do I have it right or have I goofed it up somewhere?
Have you compiled you DB lately? Also compact and repair, and there is a FAQ on a full compile on start-up. All of these may help, but it is odd.
And there is no ryme or reason? Any user at any time?
Can you describe your set-up (of the database distribution)? Is there a front End and Back End? If you move evrything to one PC (yours) does it still occur? Even if not pulling from the server?
You have to eliminate hardware/OS problems before you can totally say it is the DB. Running it locally on both a machine known to cause the fault and one that hasn't will help with that. If it runs great on a desktop, look at the server.
Perhaps record locking is playing a role (although unlikely). Does it happen with multiple users or can it happen with just one?
Sean.
And there is no ryme or reason? Any user at any time?
Can you describe your set-up (of the database distribution)? Is there a front End and Back End? If you move evrything to one PC (yours) does it still occur? Even if not pulling from the server?
You have to eliminate hardware/OS problems before you can totally say it is the DB. Running it locally on both a machine known to cause the fault and one that hasn't will help with that. If it runs great on a desktop, look at the server.
Perhaps record locking is playing a role (although unlikely). Does it happen with multiple users or can it happen with just one?
Sean.
- Thread starter
- #10
DB is compiled and I tried to run compact and repair but it is saying that it is opened exclusively on MY system! Duh... is there a way around this? Can I go to file/ open and open some other way?
When I moved the DB off the server and put it on my local drive, the problem is gone... do I need to create some type of front end back end setup on this thing? For now the DB is one sided and all users access it the same way. They are all in the file on the server. Do you think that the problems would be eliminated if I were to create front end forms, query's, etc. and place linked files on the users desktops? Would this help to eliminate the problem?
When I moved the DB off the server and put it on my local drive, the problem is gone... do I need to create some type of front end back end setup on this thing? For now the DB is one sided and all users access it the same way. They are all in the file on the server. Do you think that the problems would be eliminated if I were to create front end forms, query's, etc. and place linked files on the users desktops? Would this help to eliminate the problem?
It might, but if it works fine on a desktop, then I would be looking at the server. Perhaps uninstall and then reinstall Office on the server.
But it can't compact and repair, which means there is a problem there. Look in the folder for the .ldb (with the .mdb closed). If there is still one there, even if closed, then delete it. Also go ahead and reboot your machine. Always simulate the best possible conditions when troubleshooting. If still no dice, try to Split the database.
A database should always be split, especially if on a network and accessed by multiple user's. Make a copy of the DB copied to your desktop. Split that copy. Go ahead and try to Compact and Repair the two new split .mdb's before you go on. If the front C&R's but not the back, that would be where the problem is, and vice versa.
Then put the backend back on the server, use the Tools-->Database Utilities-->Linked table manager to refresh the tables to the new location. Then open the front end and see if the problems comes back. If so, then it's definetly the server and you will want to at least reinstall (and maybe start a thread in that OS forum ie Windoes 2000).
Let me know what happens. Sean.
But it can't compact and repair, which means there is a problem there. Look in the folder for the .ldb (with the .mdb closed). If there is still one there, even if closed, then delete it. Also go ahead and reboot your machine. Always simulate the best possible conditions when troubleshooting. If still no dice, try to Split the database.
A database should always be split, especially if on a network and accessed by multiple user's. Make a copy of the DB copied to your desktop. Split that copy. Go ahead and try to Compact and Repair the two new split .mdb's before you go on. If the front C&R's but not the back, that would be where the problem is, and vice versa.
Then put the backend back on the server, use the Tools-->Database Utilities-->Linked table manager to refresh the tables to the new location. Then open the front end and see if the problems comes back. If so, then it's definetly the server and you will want to at least reinstall (and maybe start a thread in that OS forum ie Windoes 2000).
Let me know what happens. Sean.
- Thread starter
- #12
Theres a star Sean. Thanks for all the help. I will keep working with this when everyone is out of the office and see if you latest sloution works, I think that this is the right idea. I don't know why I didn't start this with a FE and BE... oh well. Thanks again.
Chris
Chris
- Status
Similar threads
- Locked
- Question
- Locked
- Question