Modify an All Day appointment/Change Alarm time

It has come to my attention recently that in Webaccess you can create an All Day Appointment but you can't modify it once it is created (appears you would have to delete it and recreate it).
We have just migrated our Groupwise 8 installation on physical servers to Groupwise 2012 on VM. I believe that this issue existed on the Groupwise 8 Webaccess also.
Also, someone asked if it is possible to change the Alarm time of a particular appointment in Webaccess.
Any assistance would be appreciated!
Thanks,
Charlie
~~~

Originally Posted by kjhurni
How are you going about modifying the appointment?
For example:
I login to webaccess, click Calendar Tab
Click the New Appt. button
Created a regular appointment (vs. all-day event) to myself
The only way I can modify it (from my calendar) is to resend it.
I should have been clearer, this is a "Posted Appointment" set to "All Day"
If it is a Posted Appointment that is NOT an "All Day", you just double-click it and you can make changes but an "All Day" posted appointment just brings up view window and you are unable to modify it.
Are thinking there should be a "modify" option? (I don't see that in the 32-bit client either--at least on the Calendar)
Same with an all-day event.
Technically if you modify the time on any appointment (even in 32-bit client) it retracts and resends. Modifying RECIPIENTS is a diff. story, though (I believe).
I could be wrong.
Could you elaborate on what you mean by the alarm time?
I'm only aware of what's set in the Client Options (32-bit client):
Tools -> Options -> Calendar -> General
On accept, set a default alarm for BLAH
If that's what you mean, I do not see those options in the WebAccess code (in Options -> Calendar, anyway)
If I set a "Posted Appointment" in the Client, inside the Appointment form, from the Menu bar, I can select "Actions->Alarm" and change the number of minutes before the appointment that the Alarm will go off. There is nowhere in the WebAccess that you can set Alarm minutes. It appears to always set the Alarm to 5 minutes.
Thanks for any assistance you can provide!
Charlie
~~~

Similar Messages

The order of my ical 'all day' events changes when i go into print mode?

The order of my ical 'all day' events changes when i go into print mode. What can i do to keep the order of events i so painstakingly created?

IOS7: "all-day, repeating" entry from all-day to a specific time.

Since upgrading to ios7 (iPhone 5, Verizon) when using the calendar I can't switch an "all-day, repeating" entry from all-day to a specific time. There's no "all-day" toggle switch. Does anyone know how to correct this? My friend has the 5s & AT&T and she doesn't have this problem. Hers shows a toggle switch!

I haven't completely discounted it but it seems like I would need to back up to files, then restore from files. I don't want to do that. I want a full file system level SAN snapshot that I can just drop into place. The does work when the production base is shut down. However, considering that I do have archive logs, shouldn't it be possible to use them to recover to a specific scene without having to do an RMAN backup at all? It seems that doing an RMAN backup/recovery would just make this whole process a lot longer since the DB is 160 gigs in size (not huge, but the dump would take more time than I would like). With a SAN snapshot, if I can get this to work, I'm looking at about a 15-20 minute period of time to move the production DB over to test.
Since you are suggesting that RMAN may be a better approach I'll provide more details about what I'm trying to do. Essentially this is like trying to recover a DB from a server that had its power plug pulled. I was hoping that Oracle's automatic recovery would do the same thing it would do in that instance. But obviously that doesn't work. What I want to do is bring over all the datafiles, redo logs, and archive logs using the SAN snapshot. Then if possible use some aspect of Oracle (RMAN if it can do it) to mount the database, then recover to a specific time or SCN if using RMAN. However, when I tried using RMAN to do it, I got an error saying that it couldn't restore the data file because it already existed. Since I don't want to start from scratch and have RMAN rebuild files that I've already taken snapshots of (needless copying of data), I gave up on the RMAN approach. But, if you know of a way to use RMAN so that it can recover to a specific incarnation without needing to runm a backup first, I am completely open to trying it.

"Date Modified" for all files being changed if "Automatically write to XMP" is on

Recently upgraded from LR3 (v3.4.1) from LR2 on OSX 10.6.8 and have always had Catalog Settings > Automatically write changes into XMP turned on.
When browsing existing JPG files in my Library (no Develop changes, no keywording, no Presets, no Import), LR3 is writing to disk — i.e., when I look at files in Finder, almost every viewed file’s “Date Modified” is being set to today’s date and time. (It actually creates a .swp file, then changes it's name back to .jpg)
This is really bad, as it's making it impossible for me to use Finder to figure out when I last worked with a file, it is triggering needless Time Machine and Backblaze backups, and unnecessarily churning my disk.
If I turn off "Automatically write..." this behavior stops. Per David Marx at thelightroomlab.com, I tried turning off this preference, manually doing a "Save Metadata to File" for all files, letting that complete, then turning the preference back on. This does not solve the problem.
Per a suggestion at photoshop.com, I used ExifTool to see what changes LR was writing to a sample file; from the diff below, you can see that LR is adding a bunch of new fields as well as moving other fields around. But my point is that LR3 should never overwrite a file on disk if all I am doing is browsing thru them.
Is anyone else seeing this? Any ideas would be greatly appreciated!
-- David
diff Exif5609_original Exif5609_update
2c2
< FileName: DSC_5609_original.JPG
> FileName: DSC_5609_update.JPG
5,6c5,6
< FileModifyDate: 2009:11:27 21:32:54-08:00
< FilePermissions: rwxr-xr-x
> FileModifyDate: 2011:08:07 22:06:47-07:00
> FilePermissions: rw-r--r--
27a28,29
> ShutterSpeedValue: 1/200
> ApertureValue: 7.1
55d56
< SerialNumber: 3209521
75d75
< Lens: 18-200mm f/3.5-5.6
185,188d184
< UserComment:
< SubSecTime: 00
< SubSecTimeOriginal: 00
< SubSecTimeDigitized: 00
211a208,299
> XMPToolkit: Adobe XMP Core 5.2-c004 1.136881, 2010/06/10-18:11:35
> CreatorTool: Ver.1.00
> MetadataDate: 2011:08:07 22:06:47-07:00
> SerialNumber: 3209521
> LensInfo: 18-200mm f/3.5-5.6
> Lens: 18.0-200.0 mm f/3.5-5.6
> ImageNumber: 26634
> RawFileName: DSC_5609.JPG
> SavedSettingsName: Import
> SavedSettingsType: Snapshot
> SavedSettingsParametersVersion: 6.4.1
> SavedSettingsParametersProcessVersion: 5.0
> SavedSettingsParametersWhiteBalance: As Shot
> SavedSettingsParametersIncrementalTemperature: 0
> SavedSettingsParametersIncrementalTint: 0
> SavedSettingsParametersExposure: 0.00
> SavedSettingsParametersShadows: 0
> SavedSettingsParametersBrightness: 0
> SavedSettingsParametersContrast: 0
> SavedSettingsParametersSaturation: 0
> SavedSettingsParametersSharpness: 0
> SavedSettingsParametersLuminanceSmoothing: 0
> SavedSettingsParametersColorNoiseReduction: 0
> SavedSettingsParametersChromaticAberrationR: 0
> SavedSettingsParametersChromaticAberrationB: 0
> SavedSettingsParametersVignetteAmount: 0
> SavedSettingsParametersShadowTint: 0
> SavedSettingsParametersRedHue: 0
> SavedSettingsParametersRedSaturation: 0
> SavedSettingsParametersGreenHue: 0
> SavedSettingsParametersGreenSaturation: 0
> SavedSettingsParametersBlueHue: 0
> SavedSettingsParametersBlueSaturation: 0
> SavedSettingsParametersFillLight: 0
> SavedSettingsParametersVibrance: 0
> SavedSettingsParametersHighlightRecovery: 0
> SavedSettingsParametersClarity: 0
> SavedSettingsParametersDefringe: 0
> SavedSettingsParametersHueAdjustmentRed: 0
> SavedSettingsParametersHueAdjustmentOrange: 0
> SavedSettingsParametersHueAdjustmentYellow: 0
> SavedSettingsParametersHueAdjustmentGreen: 0
> SavedSettingsParametersHueAdjustmentAqua: 0
> SavedSettingsParametersHueAdjustmentBlue: 0
> SavedSettingsParametersHueAdjustmentPurple: 0
> SavedSettingsParametersHueAdjustmentMagenta: 0
> SavedSettingsParametersSaturationAdjustmentRed: 0
> SavedSettingsParametersSaturationAdjustmentOrange: 0
> SavedSettingsParametersSaturationAdjustmentYellow: 0
> SavedSettingsParametersSaturationAdjustmentGreen: 0
> SavedSettingsParametersSaturationAdjustmentAqua: 0
> SavedSettingsParametersSaturationAdjustmentBlue: 0
> SavedSettingsParametersSaturationAdjustmentPurple: 0
> SavedSettingsParametersSaturationAdjustmentMagenta: 0
> SavedSettingsParametersLuminanceAdjustmentRed: 0
> SavedSettingsParametersLuminanceAdjustmentOrange: 0
> SavedSettingsParametersLuminanceAdjustmentYellow: 0
> SavedSettingsParametersLuminanceAdjustmentGreen: 0
> SavedSettingsParametersLuminanceAdjustmentAqua: 0
> SavedSettingsParametersLuminanceAdjustmentBlue: 0
> SavedSettingsParametersLuminanceAdjustmentPurple: 0
> SavedSettingsParametersLuminanceAdjustmentMagenta: 0
> SavedSettingsParametersSplitToningShadowHue: 0
> SavedSettingsParametersSplitToningShadowSaturation: 0
> SavedSettingsParametersSplitToningHighlightHue: 0
> SavedSettingsParametersSplitToningHighlightSaturation: 0
> SavedSettingsParametersSplitToningBalance: 0
> SavedSettingsParametersParametricShadows: 0
> SavedSettingsParametersParametricDarks: 0
> SavedSettingsParametersParametricLights: 0
> SavedSettingsParametersParametricHighlights: 0
> SavedSettingsParametersParametricShadowSplit: 25
> SavedSettingsParametersParametricMidtoneSplit: 50
> SavedSettingsParametersParametricHighlightSplit: 75
> SavedSettingsParametersSharpenRadius: +1.0
> SavedSettingsParametersSharpenDetail: 25
> SavedSettingsParametersSharpenEdgeMasking: 0
> SavedSettingsParametersPostCropVignetteAmount: 0
> SavedSettingsParametersGrainAmount: 0
> SavedSettingsParametersLensProfileEnable: 0
> SavedSettingsParametersLensManualDistortionAmount: 0
> SavedSettingsParametersPerspectiveVertical: 0
> SavedSettingsParametersPerspectiveHorizontal: 0
> SavedSettingsParametersPerspectiveRotate: 0.0
> SavedSettingsParametersPerspectiveScale: 100
> SavedSettingsParametersConvertToGrayscale: False
> SavedSettingsParametersToneCurveName: Linear
> SavedSettingsParametersCameraProfile: Embedded
> SavedSettingsParametersCameraProfileDigest: D6AF5AEA62557FCE88BC099788BBD3CC
> SavedSettingsParametersLensProfileSetup: LensDefaults
> SavedSettingsParametersToneCurve: 0, 0, 255, 255
> IPTCDigest: d41d8cd98f00b204e9800998ecf8427e
228,230d315
< SubSecCreateDate: 2009:11:27 21:32:54.00
< SubSecDateTimeOriginal: 2009:11:27 21:32:54.00
< SubSecModifyDate: 2009:11:27 21:32:54.00
http://feedback.photoshop.com/photoshop_family/topics/lr3_date_modified_for_all_files_bein g_updated_when_browsing_photos_if_catalog_settings_automatically_write_changes_into_xmp_is /replies/6313647

clvrmnky wrote:
davidpope007 wrote:
Then when LR3 loaded my old LR2 images into memory, it "dirtied" the in-memory copy of the file by adding in these new LR3 XMP fields. Then, because I had "Automatically write XMP" on, it said "I better write these changes to disk".
Yuck. As a former software engineer, this is very bad software engineering.
It should wait until the user dirties the file (via Develop, keywords, etc.) before presuming to add a bunch of metadata fields that are unique to the new version of LR3.
Well, I'm a current software developer, and this is, really, a perfectly reasonable thing to do. It is a reasonable trade-off for a convenient feature required by a small subset of users.
Yes, in most cases the in-memory copy should "never" be dirtied unless the user makes a gesture of some sort, but like I said earlier, this option (once set by the user) sets up the situation where this gesture becomes implicit. This is a clear trade-off for the sake of convenience. And if the XMP is out of date and needs to be updated en masse, so be it.
The fact is, there is no easy way around this. Do we save up /every/ dirty buffer somehow until you make a gesture that /might/ require the XMP to be up-to-date before acting on that gesture? Now we have to worry about unflushed buffers if something goes wrong and the app exits. Do we save the buffers to the DB? Now we have to block some calls to make another blocking call to flush some or all of those to DB, and then write some or all of it out to one or more files. In what order? What if there is a gesture to have X files with up-to-date XMP and some or all of those are in unflushed buffers, unflushed DB writes or we have to wait for the DB.
As you can see, this is a transactionality nightmare, and the easiest and safest thing to get what the user wants (i.e., up-to-date XMP for the purpose of talking to a third-party XMP aware app) is to simply update the sidecar or XMP block in an atomic manner using the correct file IO. The file will have to change at some point, so it may as well be now.
[Thanks to both of you for your detailed replies. I am aware of the need for tradeoffs so when you say the approach taken is quite reasonable, I do believe you. I also apologize in advance for the length of the following and am extremely aware of the time it must have taken you to compose the above replies, but I'm going to add a bit more, if only for my own piece of mind and in hopes of coming up with a solution for my workflow.]
From my naive point of view, I was expecting the answer to be simply "don't raise the XMPDirtyFlag upon reading in a file". Obviously if your architecture requires you to "upgrade to latest XMP format" upon read, and another part of the system auto-detects "out of date XMP", then it's going to write those changes to disk.
But it didn't need to be designed that way. LR obviously has mechanisms to know when a user has made a change to XMP so it is able to write XMP changes to disk only when necessary.
The promise (to me) of "Automatically Write XMP changes to disk" was to auto-save my changes, and not those made for any internal (i.e., XMP versioning related) changes.
Perhaps the premise is that it is LR3's job to update an individual file's XMP to the latest version so that other XMP-aware apps can make use of it? I would argue that those third-party XMP-aware apps already have to know how to deal with all prior versions of XMP, so LR3 should just leave well enough alone.
You asked if my problem with your approach was that it was "inelegant"; not at all, it is based on my own perception of what I need from my workflow, so let me describe that so maybe we can find a better way:
* Part of the appeal of LR to me is that it preserves my original file as it came off the memory card, allowing me to move to a different workflow/toolset in 2025 if I choose to do so
* However, with all of changes contained in a single database file, I'm concerned about rare (but possible) corruption, so to mitigate this risk, I let LR backup my database weekly and it's also backed up continuously in the cloud via Backblaze
* Even with backups of the database, there is still a chance that I could lose changes made to individual files (e.g., LR corrupts the DB and I have to go back to last week's DB)
* Thus the appeal of the "auto-write to XMP" flag -- that way critical changes (develop, crop, keywords) are saved on a per-file basis; I liked the "automatic" part of this (as opposed to a manual save) because then I don't have to teach others in my family how to manually save XMP changes
* A nice side-effect of this setting is now when I use Finder to find a file and double-click on it to edit it in Photoshop, all my develop changes are right there; (in other words, I like the flexibility of not having to fire up LR in order to just invoke PS from within it); also when I use Bridge I see all the keywords there
* So with LR2, I had gotten used to what I thought was the best of all worlds -- autosave of changes at the file level via XMP + raw negatives untouched (i.e., Date Modified == the date I took the picture); this allows me to use operating-system-level tools -- Finder -- to locate/search for files
* Now I upgrade to LR3 and I'm finally now understanding that a concept "XMP versioning" is going to result in changes to many, but not all my files. (That's something else that's annoying about this issue -- I open up the Grid and browse a folder of files, and only seemingly random ones I've cursored over seem to get written to disk -- if it's so urgent that LR3 update the XMP, then it should do it for all the files in the catalog or at least in that directory)
Here's a screenshot from Finder of what I see everytime I look at this folder:
* So now I have to assume that each new version of XMP and/or LR is going to touch my files on disk. Sigh.
* What I don't like about this is that it is ruining the promise of "untouched raw negative". Yes, the image data is untouched -- which I agree is most of the benefit; but the file has been touched.
* Perhaps you might empathize a bit more if you imagined that someone went thru all your source code or Word files and randomly changed the date to "today" because you upgraded compilers or moved to Word 2011.
I agree all of this would be solved by having an XMP sidecar file for JPGs, but you indicate that's not going to happen.
You've also alluded to the solution of "resetting the Date Modifed" to it's original value -- which I believe is what Finder does when you move or copy a file -- but that that is fraught with issues as well. I believe you when you say there are issues, but again the naive part of me wonders why that soultion would be so bad...
I just thought of another potential solution -- turning on Date Created in Finder -- but it turns out that's changed, too.
I am really at a loss as to what to do and would welcome your suggestions.
Thanks again and kind regards,
-- David

All day event default alert times

I want to change the default time that I am alerted by calender for all day events. It is set on 9 am the day before but I want it to be set to noon the day before.

Limited options in Calendar/Preferences/Alerts.

Is there and app that does the following. Multiple apps are showing a clock in different rooms, all are synced together, one ipad is a master ipad and if you change the time on it all other ipads change the time

Is there and app that does the following. Multiple apps are showing a clock in different rooms, all are synced together, one ipad is a master ipad and if you change the time on it all other ipads change the time

None of the spreadsheet apps that work with Excel files offer anything like full native support in iOS. Apple's own Numbers app pairs down features for the iOS version. The hardware is simply not up to what a true computer is capable of, so all apps like QuickOffice, DocumentsToGo, Numbers and so forth offer reduced features from their computer-version counterparts.
I think a custom app will be your only real choice, be it a fully standalone app, or something built in filemaker or some other db-based platform.

All Day Events Shifts Regular time events to the Right. Unable to view meetings in portrait mode

Is there a way to view the calendar with the All Day Events and regular meetings within a portrait view.
Thanks,
BKLYN215

Same problem here; if I EVER find out the solution I will post it here.

Can I modify the the day type with a time rule???

Hello,
I´m trying to modify the day type,I want to change in some particular cases the day type from 1 to 0 for example. I´m looking in the documentation but I don´t find no operation to do this trough a time rule.
I think that it would be abble to do with a function that modify the table PSP.
Anybody knows how can I do it??
Thank you very much!!!.Regards,
Emi DF

Thank you Valéire,
I´ve solved the problem with your answer.Regards,
Emi DF

Outlook integration: All day activities are not displayed correclty

All day activities in MSA do not replicate correctly in outlook. If I create an all day activity in outlook, the activity is syncronized so I will find the appointment in outlook, but it will not be marked as all day appointment, and the time will not be from 12 am to 12 am of that day. Instead, I found that the system keeps the duration of the activity to 12 hours, but not starting and finishing in the same day.
However, when those all day appointments are created in outlook, they are refleted as all day activities in MSA so it works fine.
Thanks for your help,
ALVARO

Hi Alvaro,
Can you please tell me which version of MSA you have?
Thanks & Regards,
Rashmi

No Email Alarm for All-Day Events

Hello, Everyone,
I've got a desktop and a laptop, and I've been syncing the iCal calendars on each for some time. However, this has resulted in one annoying thing - whenever an event comes up in iCal that I'd set an email alarm for, I would receive multiple alarms, one from each machine.
I thought I'd solve this problem by moving the calendars to my server (a headless Mini running 10.4.6 Server), and thus only get one email alarm. However, since I moved it, I'm getting no alarms.
I've run some tests, and confirmed that if I set up a test event at a specific time, I will get an email alarm for it. However, if the event is set up to be an all-day event, no alarm.
I've restarted the server, I've made sure the iCalScheduler is running...these calendars have worked for years, and now I'm perplexed. Any thoughts?
Cheers,
Martin

Well, I couldn't figure this one out, so I just moved the calendars back to my main machine, and published them to the web for sharing with my laptop. On my main machine they worked fine.
Can't figure out why it wouldn't work on the server. Maybe it'll change with Leopard's iCal server.

Unwanted "Message" alarm on all-day events -- why?

I wish to create an all-day event with an email alarm. When I create the event, I enter the alarm title, check "all-day", and change the default alarm from "Message with sound" to "Email" (which defaults to "11:45 PM the day before". So the event contains only this email alarm, as I intend. After I click "Done", if I then go back and inspect this event, I find that it now has 2 alarms at the same "11:45 PM the day before", the email one I set up and a "Message with sound".
(I shouldn't need to, but) I can then edit this event to remove the "Message" alarm, but why was it added in the first place? It wasn't there when I created the event.

Jerry,
Welcome to Apple Discussions.
I would check iCal>Preferences...>General> to determine what your setting is in "Add a default alarm to all new events and invitations."
;~)

ICal all-day event default time error

Searched this discussion and others but no help there. When I create an all-day event in iCal (time zone support on, set to America/Los Angeles)it reads as Casablanca, Monrovia when synced to Entourage. Due to corp policy I'm sync'ing with Outlook Exchange server via Entourage, sync'ing Entourage with iCal, iCal with MobileMe and MobileMe with iPhone. All works just fine in regular events ... only all-day events have this incorrect default time zone.
Any ideas?

I have the same problem. All day events created in iCal sync to the Exchange server as Casablanca time zone, which I believe is the same as GMT. Events created in Entourage sync without error. Most events created on a PC with Outlook sync fine all the way through to iCal. This seemed to start about the same time as your post, ie sometime around November. Prior to some time in the fall, all day events sync'd properly. I've posted this topic to the mactopia entourage forum but I haven't gotten a response there yet.
I'm using iCal 3.0.6, Entourage 2004 11.4.0, Mac OS 10.5.6. Any thoughts anyone? Apple?

All Day events from Exchange are a day out

There are a few posts similar out there but I haven't been able to find a solution for this one.
If I create an "all day" appointment in Outlook and sync it to my iPhone via exchange it shows up a day early on the iPhone, but fine in Outlook. Now here's the interesting bit, if I modify the appointment on the iPhone and sync it back, its fine, the dates match.
I've checked the time zones and disabled time zone support, its still an issue (plus these items are a whole day out not just 13 hours so I don't think that is the issue). It sounds similar to the birthday issue here http://support.apple.com/kb/TS2456 but iTunes isn't involved so can't really do that fix.
Does anyone have any other suggestions? I'm getting a little sick of turning up to meetings a day early.
Thanks,
Cameron

I was wrong... defining a time zone in Outlook doesn't seem to change it after all.
It's a little odd because if I create an all day event and load the time zone options they are greyed out, they only become active if its not an all day event. If I save the event with the time zones showing (but greyed out) when I reopen the event the time zones are gone. So maybe nothing is actually being saved???
Its still just a theory but I suspect that saving of time zone information might be part of the problem, now I just have to find a way to prove it.

Outlook 2010 all day Event sync Problem

I have just migrated to a Bold 9900 (from a 9800 Torch) and am having problems with Outlook EVENTS. When they are synced via Desktop (7.0.0.43) they roll over and appear as a 2 day event. I am running Outlook client 2010 under Windows 7 and all was working well until I migrated from the Torch. I have checked Time zones on PC and phone and only issue I notice is that Windows 7 is using UTC while handset is GMT, but same is true for Torch 9800? Events are appear correctly as expected on Outlook.
Any suggestions greatly appreciated.
Solved!
Go to Solution.

Part of the problem appears to be that the new desktop manger software (v7, no longer intellisync) does not include the "All Day Event" flag as a a field that is synchronized between the blackberry and MS outlook. You can see that this field is no longer included in the detailed field mappings for the outlook calendar.
You can sucessfully create and sync an all day event initially. Problems begin when you later try to modify the "all day event". If you try to convert the all day event into a regular appointment at a specified time, you must "uncheck" the all day event flag on either platform (outlook or blackberry). Desktop Manager never recognizes the change in the all day event flag (since the field is not synced), which then creates a corrupt MS Outlook entry (an appointment with BOTH a specific start/end time AND also with the all day event flag checked, is mutually exclusive in MS Outlook 2010. Maybe somebody could fix this bug in next release....

Ical: won't make all day appointments on my mac but show up in iCloud..Help?

I can make appointments (using my mac air) in ical if there is a time attached but not all day appointments. The all day appointment does show up in my iCloud calendar and in fact syncs to my iphone and ipad. But can't get it to be visible in ical on my mac air. Can anyone help?

If the old account was or had been upgraded to an iCloud account as you seem to be implying, you should be able to add it back to your mac as a secondary account (system preferences > mail, calendars & contacts. This should cause both accounts calendars to show up in iCal (click the calendar button -top left corner- to confirm this. Then you should be able to copy the calendars across to your new account by following the instructions below.
Create a new empty calendar from the iCal file menu, select which account you want to create it in.
If you have only a few appointments you can move them individually by editing them and changing the calendar in the edit options.
Alternatively you can copy all the appointments in one calendar to another and delete the original.
To copy a calendar ctrl-click on it from the menu that appears when you select the calendar button (top left corner of iCal) and choose export (export it to your desktop for ease)
Double click the exported file and choose the new empty calendar to import them into.
Ctrl-click on the original calendar from the menu that appears when you select the calendar button and choose delete.
I'm guessing the reason your calendars show on your phone is because that account is enabled as a secondary account there.

Modify an All Day appointment/Change Alarm time

Similar Messages

Maybe you are looking for