AppleWorks closes accidentally when document is closed

When I close 400 page document AppleWorks closes (box appears asking if I wish to reopen or report).
Then when I reopen application and re-open the document, box asks if I wish to "recover changes because the document wasn't closed properly…" (even though the documant had been saved before closing).

Quoting Peggy's letter (PL) and my response (H):
(PL)The cause AppleWorks crashed (quit unexpectedly) the first time could be one or more of many. The most common would be a corrupt element in the document, usually a font or graphic. As this is a long document, AppleWorks may have been trying to do too many things at once or you tried to close it when it wasn't quite done doing something. Continued crashing would indicate the first cause.
First, whenever AppleWorks crashes, there is some corruption of the AppleWorks preference files & they need to be deleted before you re-launch AppleWorks. To delete AppleWorks’ preference files, go to HD > Users > Library > Preferences. Find and delete the file com.apple.appleworks.plist. Find and open the folder AppleWorks in this Preferences folder, then delete all of the enclosed files (with the exception of the Button Bar Preferences if you have customized the Button Bars). AppleWorks will recreate the preference files as it needs them.
(H) OK I've done this. Note your suggestion:"(PL)Find and open the folder AppleWorks in this Preferences folder, then delete all of the enclosed files (with the exception of the Button Bar Preferences if you have customized the Button Bars)."
(H) The only files were Excel in HD > Users > Library > Preferences > AppleWorks. I trashed them.
(PL)I recommend trying a thing or two to "clean up" the document itself.
Instead of opening this document, create a new, blank document & "Insert" (from the File menu) the problem document or drag the icon of the old document on to the the open blank document. If the corruption is in the file, not any elements, this may fix it. Save the new document with a different name.
(H) Both options (insert. drag) resulted in AppleWorks crashing.
(PL) If this didn't work, open the problem document or use the newly created one & go to File > Save As… & choose AppleWorks 5 as the file type, again with a different name. Now open this AppleWorks 5 document in AppleWorks 6. This will often strip mild corruption. You do not need to have AppleWorks 5 to do this.
(H) did this however AppleWorks still crashes when document is closed. One change has been noticed, when re-opened no longer says doc was closed improperly. Once I indicate don't try recover "lost " changes since I knew I had made none.
If the new document still has problems, remove any graphic elements. You can do this one at a time or all at once & see what happens. If you don't have any graphics or this doesn't work, try changing the font.
I don't know of any "graphic elements" unless I copied a footnote or quote and pasted it in. This document has been in the works for years.
I changed the font from palatino to Times New Roman and then redid the 5.0 to 6.0 Still crashes when doc is closed.
Well Peggy I'm most appreciative of all your woderful suggestions but still no cigar!
John
P.S. I have your "Pages" iWorks suggestion in my hip pocket waiting for after Steve Jobes' speech Jan 9. Hoping that might offer an improved software?
iBook G4 Mac OS X (10.4.8) AppleWorks 6.2.9

Similar Messages

How do I close a numbers document without closing the entire app?

Can anyone tell me how I can close a numbers document without closing the entire app? i.e. go back to the folders display page - is this even possible?

It is not a bug, but a new feature.<br />
Some menu entries in the main menu bar are hidden if you use the mouse and only appear if you use the keyboard to open the menu (Bug 626825).
You can see the difference if you use Alt+F to open the File menu or other menus like the Edit menu (Alt+E) and Bookmarks menu (Alt+B) and compare that to what you see if you use the mouse to open the menu after you have made the menu bar visible by tapping Alt or by pressing F10.
*[https://bugzilla.mozilla.org/show_bug.cgi?id=626825 bug 626825] - Hide redundant menu commands unless the user invokes the menu using the keyboard (make use of the openedWithKey attribute)
''(please do not comment in bug reports; you can vote instead)''
See also:
* [[/questions/799856#answer-155765]]

Preview doesn't close file when app is "closed"

Try this on Mountain Lion (any version):
1. Open a JPEG or PDF file in Preview, view the file (make sure it's a scratch file that you dont mind deleting).
2. Quit Preview.
3. Drag the just-viewed JPEG or PDF to the Trash.
4. Empty the Trash
At step 4, Finder will complain you cannot empty the Trash because the item you were viewing is "still in use".
5. Open Activity Monitor, locate Preview in the list of apps, Quit it (no need to force quit, normal quit will do).
6. Empty trash again. This time, the trash will empty correctly.
This is a bug. Of course, it's caused by the new "feature" of ML (and Lion) that keeps apps open after they are Quit so they can open faster (think iOS). However, clearly Preview has a bug (probably going back years) in that it clearly fails to close open files when it quits.nMy guess is this bug is old, but pre-Lion it never showed since the OS app clean up process closed the file anyway when the app quit. But today selecting "Quit" in the app menu DOESNT quit the app, and Preview sits around holding the file open, and so Trash cannot delete the file until you really, really quit Preview using Activity Monitor.
I posted this to Apple as a bug back in Lion, then again in the (then new) Mountain Lion. It's not been fixed. So either Apple can't fix it (which is pretty sad), or they dont CARE to fix it (which is worse, given how much money they make and how much I pay for Apple products).
Since "Squeaky wheels" get oiled, I'd appreciate if anyone else here is bugged by this to also post a bug report to Apple to try to get this annoying bug fixed.
--Tim

Hi Tim,
I was having this problem with several apps wanting to stay open, so I made this script applicaiton and put it in the dock:
tell application "System Events"
set app_list to (name of every process whose visible is true and name is not "QuitApps" and name is not "Finder")
end tell
repeat with this_app in app_list
tell application this_app to quit
end repeat
It has been working pretty well.
gl,

Help! adobe flash player won't install, it keeps telling me to close safari when it is closed!?

iv tried multiple times, even tried downloading adobe straight after turning the computer on and not clicking on safari at all for hours... i don't know what to do! i need adobe for work. i have a mac 13 inch retina display.. the newer version. only had it for a week. any help please

You need to close the Safari process, not just the browser window.

Pages closes after document is closed

I found the solution to this somewhere once, but it wasn't in reference to pages. Under Mavericks with Pages 5, the app will close if I've closed out the only document I've been working on and often need to restart it. Not exactly earth-shattering, but what is the setting to prevent Pages from closing when a single document is closed?

Apps closing when documents are closed is the norm on Windows and Linux.
Apple has confused matters on the Mac by sometimes doing it* and sometimes not doing it, leaving the user to puzzle out what the pattern is, or isn't.
Peter
* Notes, iWeb, Garageband, Unarchiver, Renamer, UnRARX, and others that I only notice in passing annoyance.

Auto-close Preview when last document is closed?

Is there some way to automatically close preview when all of the documents have been closed? I like to keep my active app space clear of clutter and there's no point to have a quick-loading app like Preview remain active if I've closed out everything I was reading.

Hi, isnoop.
The short answer is: no. If there were, it would be in Preview's Preferences.
You would have to Quit (Command-Q or Preview > Quit Preview) Preview.
There's no reason to quit and relaunch an application like Preview if you're going to use it more than once between restarts. It's memory footprint is small when no images are displayed and it won't use CPU cycles unless you're working with it.
Good luck!
Dr. Smoke
Author: Troubleshooting Mac® OS X

How do I close a PDF document automatically when the browser is closed?

I have a web app writen in HTML/ASP. In order to acccess this app, our users have to enter a password and user id. Once on the main page of the app, they can click on a link which opens the reader in another window. Quite often, when finished with the app, they close the browser, but leave the reader window open (with sensitive information). It is becoming to riskly to hope that they remember to close that window also, even with visual reminders. I would like for that window to close automatically when the browser with the app is closed.
Can this be done?

Let me elaborate a little more on what I am trying to do.
(1) A website (#1) is opened after entering a UID and PWD.
(2) Within website #1, a link is clicked which opens a second web app (#2) in a seperate window using window.open().
(3) Within website #2, a user can click on a link which opens a PDF as _SELF.
(4) If the user:
(a) exits out of website #1 by closing the brower
(b) we would like to automatically close the PDF from website #2 also, as this contains sensitive information and most of the time the users are forgetting to close it

Print Templates print preview window closes unexpectly when printing document

This is a cross posting from Internet Explorer Web Development after a suggestion that this forum would be a better location. See
https://social.msdn.microsoft.com/Forums/ie/en-US/351e1245-b606-4467-9f3c-1c72f9cdf9ea/print-templates-print-preview-window-closes-unexpectly-when-printing-document?forum=iewebdevelopment.
I have raised an issue through Connect for this:
https://connect.microsoft.com/IE/feedback/details/1134168/ie9-to-ie11-print-templates-print-preview-window-closes-unexpectly-when-printing-document, but I would like some more visibility of the issue as my customers thought my application was closing when
they printed a document. I also don't know if an issue in Connect gets any priority support via MSDN, but this forum does.
This looks to me like a problem in the IE Print Templates startDoc API call, but if there is a more appropriate forum to raise this issue in please let me know.
In the application where I use print templates, the window closing is not in it self a problem because the Javascript that is calling startDoc also closes the Print Preview window when the print is finished.
The fact that the application looses focus and can be hidden by the windows of other applications when the Print Preview window is closed by startDoc is the issue noticed by our customers, so I need a fix preferably, or a work around at a pinch.
Details of the issue reproduced below.
When using IE Print Templates, the startDoc function is causing the print preview window to close. This behaviour started with IE9, and is still present with IE11.
When an application is using print templates (see
https://msdn.microsoft.com/en-us/library/aa753279(v=vs.85).aspx) for print functionality, this has the effect of causing the application to become hidden by any other application window once printing from the print preview window has started. It is
actually this behaviour that started me looking at this issue as the users thought the hosting application had closed.
Print Templates are not accessible by using IE as a web browser, but only when using the WebBrowser Control to embed IE in an application. The reference for this feature is available from this url:https://msdn.microsoft.com/en-us/library/aa753279(v=vs.85).aspx
and a sample Microsoft application that demonstrates the use of Print Templates can be used to demonstrate the problem (required for the reproduction steps). The application is available via this article and searching for "download spiffy".
Steps to reproduce the problem:
To see the full effect of the issue, first ensure there is a window from another application (like Windows Explorer) that will cover the sample applications window if brought to the foreground (making the Windows Explorer window full screen works).
Start the sample application (and ensure that the full screen Window Explorer is the next application to activate).
Then in the drop down box in the top right corner of the UI select Template8.htm.
Click the Print Preview button that is just below the drop down box (this will open a new Print Preview window).
In the new window click the Print… button (this will open a Print dialog).
Click the Print button at the bottom of the Print dialog.
The Print dialog closes (expected) and then the Print Preview window also closes (not expected), however the document is still printed successfully.
When the Print Preview windows is closed unexpectedly, the Windows Explorer window is brought to the foreground (obscuring the sample applications window).
If you reselect the sample application and click the Print Preview button again, the Print Preview dialog is not displayed unless you restart the application (this looks to be a symptom of the same issue, not a separate problem).
To see that the Print Preview window appears to be closed by the startDoc call, use the resource editor in Visual Studio (the exe can be opened directly by File | Open | File…) to edit the HTML resource "TEMPLATE8.HTM" (I found I needed to delete
it and add it back in for the change to stick), find the startDoc call and add two alerts, one on the line before and one on the line after. When IE is accessing the template, it is being done using the name of the executable (so do not rename the modified
version of printtemplates.exe, make the changes to a copy in a different directory if you don't want to change the original). Start the modified version of the application and follow the same steps as in the reproduction. This time, after clicking
the Print button in the Print dialog, the dialog will close, the first alert will pop up, then the Print Preview window will close, then
the second alert will pop up.
Thank you,
Warren.

Hi Shu,
I have noticed that the print templates API is listed as part of the Legacy APIs.
Is this just because it hasn't changed or is not new? Or does this mean that it is no longer maintained and may be removed (or at least deprecated) at some point in the future?
It would good to know if we should start planning for the implementation of a different method of printing.
I understand that the sample application is no longer maintained, but I also think that the Print Template API that it uses has not changed, and so should still work (and it does mostly).
If the Print Preview window was being closed as a result of using the Print dialog (and if it had behaved the same way with IE8) I would be willing to go with the by design argument.
I have found that the Print Preview window is not closed until startDoc is called, and it closes before control is returned from the startDoc function.
Just as part of investigating and try to find a workaround, if I call window.close(), any alert calls made no longer display the alert window after the close call.
Alert still functions after startDoc has closed the window however.
The is not the sort of consistent behaviour I would expect from something that is by design.
Also while investigating, I found that calling startDoc after calling window.close() results in an exception with the error code -2147467259 (0x80004005), this is probably quite normal and expected, but does indicate that the Web Browser Control should
not be closed till after printing.
I had found that old thread, and I had concluded it was the same issue, but it was also aimed at different aspect of the problem (which I see in the sample application, but not my application).
The visible issue I have is that my users think the application has been closed because after clicking print (on the Print dialog) the application gets hidden by other windows from other applications.
This aspect affects the sample in the same manner and so it was a convenient way to demonstrate the problem.
If IE connect do not look at this issue any time soon, do I have any other avenues to resolve this issue?
Thank you,
Warren.

Call a function when the active document is closed

Hi friends
I have a portion of my script (at true a specific function) that I´d need to be executed every time the user close the app.activeDocument in Photoshop.
I know there´s a Photoshop script called "Script Event Manager" where we can associate actions and scripts with events (like closing the document). I´d not like to use this script because..as I told...it´s not my entire script to be runned when closing a file..but only a function.
Tried to search in the Script Event Manager for any event called "onClose" () but sure there´s nothing.
How could I insert an event in the body of my own script that calls a function every time user close the active document?
Thank you a lot for the help
Best Regards
Gustavo.

As I said before the close event is really not that useful. In addition to the document already being closed the event descriptor will only have the path to the closed file if it was saved as part of the close event.
But if you want to play around with this to see if it will be helpful to you here is one way. You will need to add the notifer. This only needs to be done once unless it is removed.
app.notifiersEnabled = true;
app.notifiers.add( "Cls ",new File('~/desktop/closeEventHandler.jsx') );
Then for the event handler script, something like this.
try {
    if (arguments.length >= 2) {
    var filePath;
    var desc = arguments[0];
    if( desc.hasKey( stringIDToTypeID('in') ) ) filePath = desc.getPath(stringIDToTypeID('in'));
    if( filePath != undefined ) alert( decodeURI( filePath ) );
} catch (e) {}

When Document Status will Close for AR and AP and JE.

Hi,
How we can find Document status is closed or not. My Client users are informing Particular Documents status has Closed Automatically. How it will close automatically. Is there any solution to find how it has closed?
Closed u2013 we can either close the document manually, or SAP Business One closes it automatically when you draw it to another document. Please guide me how to find out this.
Regds,
Sampath Kumar Devunuri.

Hi,
The Documents gets closed when a target document is created based on it. for example, an AR Invoice will be closed by the Incoming Payment or Credit Memo based on it.
The Status can be closed also, if the documents are reconciled through Reconciliaions.
Regards,
Jitin
SAP Business One Forum Team

Photoshop CS2 hogs RAM even when all the documents are closed.

Like the title says. I was able to re-create the issue in this video: (nevermind, I guess I can't post links)
Long story short; after having documents open, I have to close Photoshop and re-open it to get my RAM back.
Why does this happen?
Thanks in advance!

The answer is given above; that is just how it works. It shouldn't really affect your system performance much if you have enough virtual memory configured, and if you've not overdone it on the amount of RAM you allow Photoshop to use.
I just close Photoshop when I'm done using it.
-Noel

How To Close Documents Without Closing Entire App

Since the latest Pages update, when I close all open documents, it automatically closes the entire program and then I have to wait 15 minutes to start it back up. Is there any setting I can change to fix this?

That is just how long it takes the app to open up, give or take.
Version 5.1
Sometimes on my hard drive, sometimes to Apple's cloud, it has the same problem either way.

Vivado hardware server "hw_server" process doesn't close when server is closed

Vivado hardware server "hw_server" process doesn't close when server is closed.
Also, the connecting to the server hangs if a device is physically disconnected and reconnected (usually).
The "hw_server" process continually has to be killed via Task Manager, Vivado has to be closed and reopened sometimes as well.
Using Vivado 2014.1
Please fix this.

I'm on 2014.1 as well (Win7-64). I have a similar problem with 2 different PCs running the same setup. The Hardware Manager hangs while attempting some activity (usually reconfig). I click "Cancel" to dismiss the activity, which causes all of Vivado to hang. Seeing no other option, I kill Vivado in the Task Manager. However, this has the unfortunate side effect of leaving an orphaned hw_server process that can't be killed by any means, thus requiring a reboot of the PC.
This is monumentally annoying.
Can someone comment on whether this is due to a known issue, and if it's fixed in 2014.2?

Firefox 10.0.2 doesn't delete cookies when Firefox is closed when selecting: Keep until: I close Firefox:

From the Menu bar select + tools + options + privacy + use custom settings for history + Keep until: I close Firefox:
Firefox 10.0.2 doesn't delete cookies when Firefox is closed when selecting: Keep until: I close Firefox: Please advise Thanks :)

If you change that cookie setting at a later time then only new cookies are affected and you need to remove already existing cookies yourself.
There are also extensions that add opt-out cookies that can't be removed as long as the extension is installed (enabled).

Is there a way to close VI's nicely when Window is closed with "X"?

Is there a way to close VI's nicely when Window is closed with "X"?
The VI is the GUI for an automated test console and I would like to save a state when it is closed to allow for the user to reopen the VI and the GUI is the same. At the very least I would like to make sure the equipment is placed into a safe state.
-Nate

Dennis, I could not find the VI you mentioned. How do you search on a vi's name in Labview? I even tried with Windows Explorer search and didn't find it.
What I did find was that you need to use the "Panel Close?" filter event to catch clicking on the X, and the "Application Instance Close?" filter event to catch clicking on the menu bar File - Exit. The attached vi does just this.
- tbob
Inventor of the WORM Global
Attachments:
CatchClose.vi ‏11 KB

AppleWorks closes accidentally when document is closed

Similar Messages

Maybe you are looking for