My company's going through a (painful) migration to Office 2003 and we
currently have XP users with Outlook 2003 and two groups of NT users, some
with Outlook 98 but most with 2000. An essential custom form has been landed
on my desk to be fixed - I say this because I want to make clear I didn't
develop it and am only just starting to puzzle out the VB script behind it
(over 125 pages when pasted into Word). It works fine in 98 and 2003 but
causes an access violation in 2000 the moment you click on Send and Dr Watson
immediately takes over.

Any ideas where I should start looking? I'm used to working in VBA with all
its handy debugging tools and am unclear as to where to start! The form is
based on an external database (Access) and reads/updates that as well as well
as being sent to a fixed address within the company.

Thanks for any clues...

Create a new message using the form.
Choose Tools | Forms | Script Debugger
Put a breakpoint in the Item_Send handler.
Step through the code until you hit the error.

--
Sue Mosher, Outlook MVP
Author of Configuring Microsoft Outlook 2003
http://www.turtleflock.com/olconfig/index.htm
and Microsoft Outlook Programming - Jumpstart for
Administrators, Power Users, and Developers
http://www.outlookcode.com/jumpstart.aspx

"Martin" wrote in message ...
My company's going through a (painful) migration to Office 2003 and we
currently have XP users with Outlook 2003 and two groups of NT users, some
with Outlook 98 but most with 2000. An essential custom form has been landed
on my desk to be fixed - I say this because I want to make clear I didn't
develop it and am only just starting to puzzle out the VB script behind it
(over 125 pages when pasted into Word). It works fine in 98 and 2003 but
causes an access violation in 2000 the moment you click on Send and Dr Watson
immediately takes over.

Any ideas where I should start looking? I'm used to working in VBA with all
its handy debugging tools and am unclear as to where to start! The form is
based on an external database (Access) and reads/updates that as well as well
as being sent to a fixed address within the company.

Thanks for any clues...

Thanks Sue. Unfortunately that feature isn't installed on my machine.
Instead, I deleted the Item_Sent procedure (leaving the Sub and End Sub
lines) and republished the form in Outlook 98 to a temp name. When I created
a new message based on this in Outlook 2000 (I have this set up on another
machine), it crashed again in an identical way.

What other handlers are triggered by clicking Send? Hmm, I've just spotted
"Item_CustomPropertyChange"...

"Sue Mosher [MVP-Outlook]" wrote:

Create a new message using the form.
Choose Tools | Forms | Script Debugger
Put a breakpoint in the Item_Send handler.
Step through the code until you hit the error.

--
Sue Mosher, Outlook MVP
Author of Configuring Microsoft Outlook 2003
http://www.turtleflock.com/olconfig/index.htm
and Microsoft Outlook Programming - Jumpstart for
Administrators, Power Users, and Developers
http://www.outlookcode.com/jumpstart.aspx

"Martin" wrote in message ...
My company's going through a (painful) migration to Office 2003 and we
currently have XP users with Outlook 2003 and two groups of NT users, some
with Outlook 98 but most with 2000. An essential custom form has been landed
on my desk to be fixed - I say this because I want to make clear I didn't
develop it and am only just starting to puzzle out the VB script behind it
(over 125 pages when pasted into Word). It works fine in 98 and 2003 but
causes an access violation in 2000 the moment you click on Send and Dr Watson
immediately takes over.

Any ideas where I should start looking? I'm used to working in VBA with all
its handy debugging tools and am unclear as to where to start! The form is
based on an external database (Access) and reads/updates that as well as well
as being sent to a fixed address within the company.

Thanks for any clues...

You can get the script debugger installed like this: Rerun Outlook/Office setup, and under Office Tools, install the HTML Source Editing/ Web Scripting / Web Debugging feature.

Item_Write would also be called, but only after Item_Send.

--
Sue Mosher, Outlook MVP
Author of Configuring Microsoft Outlook 2003
http://www.turtleflock.com/olconfig/index.htm
and Microsoft Outlook Programming - Jumpstart for
Administrators, Power Users, and Developers
http://www.outlookcode.com/jumpstart.aspx

"Martin" wrote in message ...
Thanks Sue. Unfortunately that feature isn't installed on my machine.
Instead, I deleted the Item_Sent procedure (leaving the Sub and End Sub
lines) and republished the form in Outlook 98 to a temp name. When I created
a new message based on this in Outlook 2000 (I have this set up on another
machine), it crashed again in an identical way.

What other handlers are triggered by clicking Send? Hmm, I've just spotted
"Item_CustomPropertyChange"...

"Sue Mosher [MVP-Outlook]" wrote:

Create a new message using the form.
Choose Tools | Forms | Script Debugger
Put a breakpoint in the Item_Send handler.
Step through the code until you hit the error.

"Martin" wrote in message ...
My company's going through a (painful) migration to Office 2003 and we
currently have XP users with Outlook 2003 and two groups of NT users, some
with Outlook 98 but most with 2000. An essential custom form has been landed
on my desk to be fixed - I say this because I want to make clear I didn't
develop it and am only just starting to puzzle out the VB script behind it
(over 125 pages when pasted into Word). It works fine in 98 and 2003 but
causes an access violation in 2000 the moment you click on Send and Dr Watson
immediately takes over.

Any ideas where I should start looking? I'm used to working in VBA with all
its handy debugging tools and am unclear as to where to start! The form is
based on an external database (Access) and reads/updates that as well as well
as being sent to a fixed address within the company.

Thanks for any clues...

No that didn't work - I've cut out all Item_ events and, even if I just
create a new message and type nothing at all, it still crashes when I click
Send.

Feels like some sort of corruption but it's strange because the identical
form works fine in both 98 and 2003. I've tried making/undoing some design
changes in 2000 itself and republishing in 2000 but still no joy.

Any suggestions welcome...(!)

"Martin" wrote:

Thanks Sue. Unfortunately that feature isn't installed on my machine.
Instead, I deleted the Item_Sent procedure (leaving the Sub and End Sub
lines) and republished the form in Outlook 98 to a temp name. When I created
a new message based on this in Outlook 2000 (I have this set up on another
machine), it crashed again in an identical way.

What other handlers are triggered by clicking Send? Hmm, I've just spotted
"Item_CustomPropertyChange"...

"Sue Mosher [MVP-Outlook]" wrote:

Create a new message using the form.
Choose Tools | Forms | Script Debugger
Put a breakpoint in the Item_Send handler.
Step through the code until you hit the error.

--
Sue Mosher, Outlook MVP
Author of Configuring Microsoft Outlook 2003
http://www.turtleflock.com/olconfig/index.htm
and Microsoft Outlook Programming - Jumpstart for
Administrators, Power Users, and Developers
http://www.outlookcode.com/jumpstart.aspx

"Martin" wrote in message ...
My company's going through a (painful) migration to Office 2003 and we
currently have XP users with Outlook 2003 and two groups of NT users, some
with Outlook 98 but most with 2000. An essential custom form has been landed
on my desk to be fixed - I say this because I want to make clear I didn't
develop it and am only just starting to puzzle out the VB script behind it
(over 125 pages when pasted into Word). It works fine in 98 and 2003 but
causes an access violation in 2000 the moment you click on Send and Dr Watson
immediately takes over.

Any ideas where I should start looking? I'm used to working in VBA with all
its handy debugging tools and am unclear as to where to start! The form is
based on an external database (Access) and reads/updates that as well as well
as being sent to a fixed address within the company.

Thanks for any clues...

Sounds like a pretty dead form. Are you working from an .oft file or a published form definition? You might try republishing with Outlook 2003 to see if it behaves better then. Worst case is that you'll have to start from scratch with a new form, build up the pages with controls, then copy/paste the old code.

Or weight the cost of that against the cost of accelerating the upgrade of the Outlook 2000 users.

--
Sue Mosher, Outlook MVP
Author of Configuring Microsoft Outlook 2003
http://www.turtleflock.com/olconfig/index.htm
and Microsoft Outlook Programming - Jumpstart for
Administrators, Power Users, and Developers
http://www.outlookcode.com/jumpstart.aspx

"Martin" wrote in message ...
No that didn't work - I've cut out all Item_ events and, even if I just
create a new message and type nothing at all, it still crashes when I click
Send.

Feels like some sort of corruption but it's strange because the identical
form works fine in both 98 and 2003. I've tried making/undoing some design
changes in 2000 itself and republishing in 2000 but still no joy.

Any suggestions welcome...(!)

"Martin" wrote:

Thanks Sue. Unfortunately that feature isn't installed on my machine.
Instead, I deleted the Item_Sent procedure (leaving the Sub and End Sub
lines) and republished the form in Outlook 98 to a temp name. When I created
a new message based on this in Outlook 2000 (I have this set up on another
machine), it crashed again in an identical way.

What other handlers are triggered by clicking Send? Hmm, I've just spotted
"Item_CustomPropertyChange"...

"Sue Mosher [MVP-Outlook]" wrote:

Create a new message using the form.
Choose Tools | Forms | Script Debugger
Put a breakpoint in the Item_Send handler.
Step through the code until you hit the error.

"Martin" wrote in message ...
My company's going through a (painful) migration to Office 2003 and we
currently have XP users with Outlook 2003 and two groups of NT users, some
with Outlook 98 but most with 2000. An essential custom form has been landed
on my desk to be fixed - I say this because I want to make clear I didn't
develop it and am only just starting to puzzle out the VB script behind it
(over 125 pages when pasted into Word). It works fine in 98 and 2003 but
causes an access violation in 2000 the moment you click on Send and Dr Watson
immediately takes over.

Any ideas where I should start looking? I'm used to working in VBA with all
its handy debugging tools and am unclear as to where to start! The form is
based on an external database (Access) and reads/updates that as well as well
as being sent to a fixed address within the company.

Thanks for any clues...

Thanks for your help Sue. I'm going to try rebuilding the form you suggest.
It is odd though that 2003 and 98 are both happy with the current published
form and it's only 2000 that crashes.

If anyone has any further ideas, I'd be very grateful to hear them.


"Sue Mosher [MVP-Outlook]" wrote:

You can get the script debugger installed like this: Rerun Outlook/Office setup, and under Office Tools, install the HTML Source Editing/ Web Scripting / Web Debugging feature.

Item_Write would also be called, but only after Item_Send.

--
Sue Mosher, Outlook MVP
Author of Configuring Microsoft Outlook 2003
http://www.turtleflock.com/olconfig/index.htm
and Microsoft Outlook Programming - Jumpstart for
Administrators, Power Users, and Developers
http://www.outlookcode.com/jumpstart.aspx

"Martin" wrote in message ...
Thanks Sue. Unfortunately that feature isn't installed on my machine.
Instead, I deleted the Item_Sent procedure (leaving the Sub and End Sub
lines) and republished the form in Outlook 98 to a temp name. When I created
a new message based on this in Outlook 2000 (I have this set up on another
machine), it crashed again in an identical way.

What other handlers are triggered by clicking Send? Hmm, I've just spotted
"Item_CustomPropertyChange"...

"Sue Mosher [MVP-Outlook]" wrote:

Create a new message using the form.
Choose Tools | Forms | Script Debugger
Put a breakpoint in the Item_Send handler.
Step through the code until you hit the error.

"Martin" wrote in message ...
My company's going through a (painful) migration to Office 2003 and we
currently have XP users with Outlook 2003 and two groups of NT users, some
with Outlook 98 but most with 2000. An essential custom form has been landed
on my desk to be fixed - I say this because I want to make clear I didn't
develop it and am only just starting to puzzle out the VB script behind it
(over 125 pages when pasted into Word). It works fine in 98 and 2003 but
causes an access violation in 2000 the moment you click on Send and Dr Watson
immediately takes over.

Any ideas where I should start looking? I'm used to working in VBA with all
its handy debugging tools and am unclear as to where to start! The form is
based on an external database (Access) and reads/updates that as well as well
as being sent to a fixed address within the company.

Thanks for any clues...