Object variable not set in Calendar Preferences

One of our clients have the problem that viewing the calendar the time is shown from 0:00 till 0:00 (or 23:59 if you like…).

Setting the preferences in the calendar preferences gives an error when pressing OK.

Message:

Object VAriable not set

On module CLICK

On line 32

On method CLICK

I notices a similar problem in this thread: http://www-10.lotus.com/ldd/nd8forum.nsf/5f27803bba85d8e285256bf10054620d/e2e31db8b9afcdbf8525749f002c8c56?OpenDocument but alas no solution is there.

Alas deleting the workspace dir. or the cache.ndk gives no result.

Could anyone help me out on this?

The client is just upgraded from R703 to R802.

Regards,

Peter

Subject: Calendar Profile

Try deleting the calendar profile from the mail file. You may do this by using the following lotusscript:

Sub Click(Source As Button)

Dim session As New NotesSession

Dim db As NotesDatabase

Dim doc As NotesDocument

Set db=session.CurrentDatabase

Set doc=db.GetProfileDocument(“CalendarProfile”)

Call doc.remove(True)

Msgbox “Profile Document is Successfully Removed”

End Sub

Subject: I’ve encountered same thing

I’ve encountered a similar situation, except I got the error message when I tried to change the access and delegation. It only happened to a certain user though. What I did to resolve this was to convert the mailfile back down to 7, then converted back to 8. This seemed to have worked for me.

HTH

Subject: Tx I’ll try it

When I am at the customr again (next week).I’ll let you know how and if I solved it.

Regards,

Peter

Subject: Alas no solution

It seems to be a client option. The same database works fine on my machine.Removing workspace dir and cache.ndk is no solution

Subject: Its problem with ACL

Whoever is trying to update the Preferences, i.e. CalendarProfile his/her name should be there in the ACL. The code is looking for preson’s name in ACL. If it’s not there then it returns a “” value.

If your name is not there in the ACL individually, not in a group, then try adding it with Manager access. The update the doc, it would work absolutely fine.

It worked for me today. The issue was happening in 2 DBs and I found there were no Owner assigned in the ACL. Thus they were getting error. After I added my name as Manager and then saved the profile - it worked fine.