Word VBA User Form causes DDE Timeout dialogue box

We have a read only Word document on our intranet which we wish users to open and then complete. Based on information they give a seperate document is saved to Worksite and another inhouse system updated.

To gather the users information we use a custom Word form which opens at the Word documents "on open" event.

However, this approach is generating a "DDE Timeout, application could not be started error" from Worksite.

The error can be OK'd and does not affect the behaviour of the form or the document.

What we would like to know is:

- What's Worksite expecting to be returned from Word, when opening a document?
- How can we emulate this value to remove the error message?

Find more posts tagged with

Comments

jny

If you could provide the following, I can then take a look at it:

- A reproducible project, i.e., your AddIn or template that can reproduce this behavior.

- A set of steps to run to encounter the behavior.

- The version of WorkSite.

- The Office Integration Mode, i.e, Enhanced Application Integration (EAI) or Classic.

Migrateduser

Thanks, in answer to your points:

- Create a new Word document. Create a Word VBA user form and set this to display on the documents On Open event. Save the document to Worksite, reopen and wait (leave the form open), the error should display shortly.

- Worksite 8

- EAI (I think)

jny

If you could send in a macro that can reproduce that, I can then take a look at it.

Migrateduser

Please find sample attached.

Just save this into iManage / Mailsite, open the document from the database to which it has been saved and wait for the error to appear.

jny

I am unable to reproduce the same error you have encountered with the following steps:

1. Unzipped your attachment.
2. Imported the Form Sample.doc to FileSite.
3. Opened the imported document.

No DDE timeout.

You have only mentioned you have version 8. I don't know which specific version that is, i.e., 8.0, 8.1, or 8.2. But judging from your rerference to IManage/MailSite, this tells me you probably have 8.0.

Do you have the most recent version, 8.2 SP1, to test this? I tested it without any problems, based on the above steps, in FileSite 8.2 SP1 and Office 2007.

jny

I also just tested in 8.0 SP1, and I see the time out behavior. It looks like this might have been fixed in the later versions, as I wasn't able to reproduce this in 8.2 SP1.

d_rewb

Hi,
there guys I think i have a similar problem, and have tried to have a look at the code, but i am iam new to this all, its a little difficult. Would anyone be able to help with this.

When ever the form is generated i get a "Microsoft visual basic box" if i am correct it seems as though its missing an addin of some sort.

I have attached a sample of the document and the error message pic...

any help would be much appreciated.

thanks

A

Migrateduser

We are using Worksite 8.0 @ SP1.

Just as you have so very kindly confirmed this generates the error.

If our error will be fixed by a service pack then that's good to know, I will ask our users to 'sit tight' until this has been installed on our systems.

Many Thanks (and thanks for your patience)!

Migrateduser

For d_rewb

Are these problem documents created from a template? There appears to be no supporting macro code in the sample.

However, looking at the error dialogue this looks Word generated - Worksite / iManage in my experience produces error messages labeled as such.

Does your Normal.dot or do any of your addins attempting to run code against documents as these are opened? And can these cope with the situation where a document has been form protected? This would be my first line of investigation, so I'd also look at your addins and Normal.dot for the phrase:

On Error goto... [label]

find the labed error procedures and then look for code like the following:

MsgBox "", vbMsgBoxHelpButton + vbCritical

This would rule out any interaction between your form and your Word set-ups custom coding / macors.

d_rewb

Thanks for the reply....

thats exactly it i believe the guy that set it all up said all we needed is an add-in, which being new to all this completely confusing. However i have been reading the code, and getting to grips with it...

The scenario is we have a form that everyone fills in, we then have documents on the database that have blank spaces in them so that whenever the form is completed, a user then decideds which document they would like to send the info to, and from there it autofills everything...when we had this filesite setup about a week ago, these are the problems that occured...

I have looked at the normal.dot, but your right in saying theres a conflict somewhere with the form code and macros...

I will try and see if i can create something new from scratch...

once again thanks