VBA - My Outlook Calendar.dot

Status
Not open for further replies.

Abenser

Member
I having problems using the My Outlook Calendar.dot template from the Slipstick website (sorry I can't attach it, file type not supported).




I downloaded the .dot file and with the help of someone in IT we modified the code to pull event details from outlook onto the resulting calendar report. I was able to use it successfully for a few weeks and then all of a sudden the .dot stopped working. It gives me a runtime error whenever I try to launch it.




I'm not familiar with VBA at all but I used the debug tool to see where the code "breaks". It seems to happen at Ln 3046 - 3047. Now, I could be completely wrong on that one - but I thought I'd take a stab.




I have tried using the .dot file on other machines on the network and I get varying results. Some machines give a runtime error on first launch. On others, I can use it for a few times and then I get the runtime error. There is no pattern that I can see, but thought I'd post this on the forum to see if anyone else has had issues with the My Outlook Calendar.dot file or could look at the code and tell me what's up.




Thanks for your time - Angela
 
K

Ken Slovak - [MVP - Outlook]

If the code in the form was modified then there's no way anyone could figure

out why your version is failing from looking at the original code.

"Abenser" <Abenser.477sya@invalid> wrote in message

news:Abenser.477sya@invalid...

> I having problems using the My Outlook Calendar.dot template from the
> Slipstick website (sorry I can't attach it, file type not supported).

> I downloaded the .dot file and with the help of someone in IT we
> modified the code to pull event details from outlook onto the resulting
> calendar report. I was able to use it successfully for a few weeks and
> then all of a sudden the .dot stopped working. It gives me a runtime
> error whenever I try to launch it.

> I'm not familiar with VBA at all but I used the debug tool to see where
> the code "breaks". It seems to happen at Ln 3046 - 3047. Now, I could be
> completely wrong on that one - but I thought I'd take a stab.

> I have tried using the .dot file on other machines on the network and I
> get varying results. Some machines give a runtime error on first launch.
> On others, I can use it for a few times and then I get the runtime
> error. There is no pattern that I can see, but thought I'd post this on
> the forum to see if anyone else has had issues with the My Outlook
> Calendar.dot file or could look at the code and tell me what's up.

> Thanks for your time - Angela

> > Abenser
> >
 

Abenser

Member
We only modified the section of the code that pulled fields from outlook onto the resulting .doc, nothing else. And, the .dot worked fine after that for a few weeks and then something happened and it doesn't work for me now.




I think I need to hire someone that knows VBA and can look at the solution and see what is happening in our environment that is causing this thing to buck.




FYI - I've been sucessful in running the modified .dot on other machines in the office - some not all will give the error, and then eventually running the .dot on those machines will bring the runtime error. One machine in the office currently still can run the .dot with no error and I can print the calendar needed. I anticipate that this work around will eventually fail. I'm ust trying to figure out what's going on before I get the runtime error on that machine so I can continue to provide a calendar erport to the boss.




- A




Thanks
 
K

Ken Slovak - [MVP - Outlook]

From what you say you first need to figure out what's different where it

works and where it doesn't work. Once that's solved you should be able to

get it working everywhere.

"Abenser" <Abenser.479b4a@invalid> wrote in message

news:Abenser.479b4a@invalid...

> We only modified the section of the code that pulled fields from outlook
> onto the resulting .doc, nothing else. And, the .dot worked fine after
> that for a few weeks and then something happened and it doesn't work for
> me now.

> I think I need to hire someone that knows VBA and can look at the
> solution and see what is happening in our environment that is causing
> this thing to buck.

> FYI - I've been sucessful in running the modified .dot on other
> machines in the office - some not all will give the error, and then
> eventually running the .dot on those machines will bring the runtime
> error. One machine in the office currently still can run the .dot with
> no error and I can print the calendar needed. I anticipate that this
> work around will eventually fail. I'm ust trying to figure out what's
> going on before I get the runtime error on that machine so I can
> continue to provide a calendar erport to the boss.

> - A

> Thanks

> > Abenser
> >
 

Abenser

Member
OK. I'm going to show this thread to IT. They think it's the code and that they can't fix it cuz they didn't write it. But if it works for some, not all, it is environment, right? Hmmm...it's a mystery is what it is. Thanks for contributing. I will let you all know if I figure anything out.




A
 
Status
Not open for further replies.
Top