Outlook Upgrade to 2003

  • Thread starter Thread starter Anthony Smith
  • Start date Start date
A

Anthony Smith

Good Afternoon,

I recently upgrade from Office XP to Office 2003. Like the new Outlook. Has
a few things in there I have to get used to though.

I have a problem. I had a custom made form that was used in the older
version. When I could right click on a customer and create a (appointment or
task or journal entry) it would open the custom form. The reason for the
custom form was to save the appointment/task/journal entry to the public
folders for everyone to access. Well when I do this now, It opens the form
and when I close it, it pops up with an operation error. I click ok, and
everything's ok. I look in the P.F. calendar, and the appointment is there
with the link to the contact. So why am I getting this error?

I remember a previous upgrade, I had to change some settings from Outlook 9
to Outlook 10 or something. Because I used that tool from slipstick that
helps with custom forms. Like a use this form tool, forgot what it's called
though. It allows you to substitue another form, for the default form used.

Thanks for the help!

--

Sincerely,
Anthony Smith
Power Equipment Company
(e-mail address removed)
www.peconet.com
 
Is this in a public folder? You should not attempt to access any public folder that contains custom forms using the Public Folder\Favorites hierarchy.

See http://www.slipstick.com/dev/newdefaultform.htm#changedefault on the forms substitution tool. I have not tried forms substitution in Outlook 2003.

--
Sue Mosher, Outlook MVP
Outlook and Exchange solutions at http://www.slipstick.com
Author of
Microsoft Outlook Programming: Jumpstart
for Administrators, Power Users, and Developers
 
Good Morning Sue,

How are you? I'm blessed. Yes it is in public folders. The calendar,
contacts, tasks, journal entries are in P.F.s. So when I do a
activity(appointment, task, etc.) I want it to store it in the public
folders.

Here is the exact error message:
Could not complete the operation. One or more parameter values are not
valid.

Now as I stated it copies it to the calendar folder, but I'm still getting
this error everytime. I dont' know how to stop the error. Thanks for your
help.


--

Sincerely,
Anthony Smith
Power Equipment Company
(e-mail address removed)
www.peconet.com
Is this in a public folder? You should not attempt to access any public
folder that contains custom forms using the Public Folder\Favorites
hierarchy.

See http://www.slipstick.com/dev/newdefaultform.htm#changedefault on the
forms substitution tool. I have not tried forms substitution in Outlook
2003.

--
Sue Mosher, Outlook MVP
Outlook and Exchange solutions at http://www.slipstick.com
Author of
Microsoft Outlook Programming: Jumpstart
for Administrators, Power Users, and Developers
 
That's a very non-specific error message that can have a number of causes, most of which seem to be related to corruption of a property in the item. I didn't see any articles in the MSKB about it just for Outlook 2003, but you might check out the articles listed in this query:

http://support.microsoft.com/search...pe=PHRASE&maxResults=25&Titles=false&numDays=

If the error persists or occurs frequently, it might be helpful is to get exact steps on how someone else might reproduce it.

Do note my earlier warning on the incompatibility between custom forms and PF Favorites.
 
Good Afternoon Sue,

I went the the KB article and did what it told me in KB 320842, changed data
files to .old and created a new profile. I'm still getting the error...
"Could not complete the operation. One or more parameter values are not
valid."
As I stated before it actually puts the appointment in the public folder
(not favorites) but I still get this error.

Here is the code in the custom calendar form:
Option Explicit

Const olDiscard = 1

Const olAppointment = 26

Const olJournal = 42

Dim mstrTargetFolder

Dim mblnSaveInTarget

Dim mblnResetStart

Sub InitOpts()

' #### USER OPTIONS ####

' set path to target folder here

mstrTargetFolder = "Public Folders/All Public Folders/Power
Equipment/Calendar"

' reset Start date to Now, rather than published form date

mblnResetStart = True

End Sub



Function Item_Open()

If Item.Size = 0 Then

' for appointments and journal items, set Start

' according to option in InitOpts

If mblnResetStart Then

If Item.Class = olAppointment Or _

Item.Class = olJournal Then

Item.Start = Now

End If

End If

If Item.BillingInformation <> "IsCopy" Then

mblnSaveInTarget = True

Call InitOpts

End If

End If

End Function



Function Item_Write()

Dim objCopy

Dim objTargetFolder

If mblnSaveInTarget And Not Item.Saved Then

Set objTargetFolder = GetMAPIFolder(mstrTargetFolder)

If Not objTargetFolder Is Nothing Then

Item.BillingInformation = "IsCopy"

Set objCopy = Item.Copy

objCopy.Move objTargetFolder

Item_Write = False

Item.Close olDiscard

End If

End If

Set objCopy = Nothing

Set objTargetFolder = Nothing

End Function


Function GetMAPIFolder(strName)

Dim objNS

Dim objFolder

Dim objFolders

Dim arrName

Dim I

Dim blnFound

Set objNS = Application.GetNamespace("MAPI")

arrName = Split(strName, "/")

Set objFolders = objNS.Folders

blnFound = False

For I = 0 To UBound(arrName)

For Each objFolder In objFolders

If objFolder.Name = arrName(I) Then

Set objFolders = objFolder.Folders

blnFound = True

Exit For

Else

blnFound = False

End If

Next

If blnFound = False Then

Exit For

End If

Next

If blnFound = True Then

Set GetMAPIFolder = objFolder

End If

Set objNS = Nothing

Set objFolder = Nothing

Set objFolders = Nothing

End Function




Please let me know if you see what might be causing this error. Thanks!

Anthony....




That's a very non-specific error message that can have a number of causes,
most of which seem to be related to corruption of a property in the item. I
didn't see any articles in the MSKB about it just for Outlook 2003, but you
might check out the articles listed in this query:

http://support.microsoft.com/search...pe=PHRASE&maxResults=25&Titles=false&numDays=

If the error persists or occurs frequently, it might be helpful is to get
exact steps on how someone else might reproduce it.

Do note my earlier warning on the incompatibility between custom forms and
PF Favorites.
 
Still fishing here: Where is the form published? Did you try stepping through the code to determine exactly when that error message is occurring? Are you using the registry entry to substitute your form for the default?
--
Sue Mosher, Outlook MVP
Outlook and Exchange solutions at http://www.slipstick.com
Author of
Microsoft Outlook Programming: Jumpstart
for Administrators, Power Users, and Developers
 
It's published in the Organizational Forms Library. No, I haven't tried
stepping through the code yet. Yes I am using that ChangeForms file to
generate the registry entry to substitute the form default.
I did not change any entries after I upgraded from Outlook 2002 to Outlook
2003.

I remember when I upgrade to XP, I had to change the settings from
Outlook9.0, to Outlook 10.0 in the registry file. Do I have to do that for
this one also?

It's strange, it's does everything I want it do, but it produces an error
anyway?
Also it does not produce this error, when I create a Task or Journal entry
from a contact. I normally right click on a contact and create the desired
appt/task/jentry.

Thanks for the help!
Still fishing here: Where is the form published? Did you try stepping
through the code to determine exactly when that error message is occurring?
Are you using the registry entry to substitute your form for the default?
--
Sue Mosher, Outlook MVP
Outlook and Exchange solutions at http://www.slipstick.com
Author of
Microsoft Outlook Programming: Jumpstart
for Administrators, Power Users, and Developers
 
I remember when I upgrade to XP, I had to change the settings from
Outlook9.0, to Outlook 10.0 in the registry file. Do I have to do that for
this one also?

Yes, of course. Each version of Outlook has its own key in the registry.

Please keep us posted. There have been some other posts about problems with forms substitution on Outlook 2003, and I'm beginning to wonder if they're all related.

FYI, there is a separate newsgroup for Outlook forms issues -- microsoft.public.outlook.program_forms. --
Sue Mosher, Outlook MVP
Outlook and Exchange solutions at http://www.slipstick.com
Author of
Microsoft Outlook Programming: Jumpstart
for Administrators, Power Users, and Developers
 
Back
Top