Replies

tough problem. it looks like something is corrupting the registry.
you might want to try the following (make sure no instances of word are running – if you’re not sure, reboot the computer)
now click start->run and enter “winword /r” (according to mskb the switch for word2000 is /r (and not /regserver)) without the quotes and press enter. this will reregister word’s automation classes.
also, iirc, the ‘set x=new “classname”‘ construct bypasses some stages in the creation of a class instance, so your problem could possibly be solved by using a
dim loWd as word.application
Set loWd = createobject(“word.application”)
note:you can still use early binding for this statement and all your other statements if you leave the reference to the word object library.

“When opening an office document that expects user interaction my app is hanging.”

in general, you could avoid user interaction by setting various properties before/at opening of an office document. maybe this can avoid the serverbusytime.
in word for example, you can aplly properties to autoconfirm conversions, disable automacros and so on, the same goes for excel.
in access, it is no problem if that database has an opening form afaict (at least in my limited testing), only when this form start running code immediately this could (not tested) lead to timeouts. also, have you considered using ADO to open the database instead of creating an access instance

“When opening an office document that expects user interaction my app is hanging.”

in general, you could avoid user interaction by setting various properties before/at opening of an office document. maybe this can avoid the serverbusytime.
in word for example, you can aplly properties to autoconfirm conversions, disable automacros and so on, the same goes for excel.
in access, it is no problem if that database has an opening form afaict (at least in my limited testing), only when this form start running code immediately this could (not tested) lead to timeouts. also, have you considered using ADO to open the database instead of creating an access instance

these are all sane arguments of course. a template should be as selfcontaining as possible, whilst still allowing user customization. setting the normal template to read only does limit user customization, so in this sense comments 1 & 2 are slightly contradictory if one really wants to start nitpicking that is

these are all sane arguments of course. a template should be as selfcontaining as possible, whilst still allowing user customization. setting the normal template to read only does limit user customization, so in this sense comments 1 & 2 are slightly contradictory if one really wants to start nitpicking that is

if the template is not in the startupfolder of word (options.DefaultFilePath(wdStartupPath)) it won’t load automatically.
either put it in the startup folder or use the add method of the addins object to load it.

if the template is not in the startupfolder of word (options.DefaultFilePath(wdStartupPath)) it won’t load automatically.
either put it in the startup folder or use the add method of the addins object to load it.

just a quick idea to explore:how about copying the entire commandbar and keep track of custom controls. you could set various properties of the copied commandbar to provide some basic form of preventing to user to tamper with them.

just a quick idea to explore:how about copying the entire commandbar and keep track of custom controls. you could set various properties of the copied commandbar to provide some basic form of preventing to user to tamper with them.

great tip. i combine mvps’s host file with hpguru’s one. i look for updates on security sofware (including several hosts list definitions) at the calendar of security updates

great tip. i combine mvps’s host file with hpguru’s one. i look for updates on security sofware (including several hosts list definitions) at the calendar of security updates

nice! NOT!
here’s the most recent phishing scam which in essence exploits bad html design on the server, which allows cross site script injection (for instance mastercard.com is vulnerable)
http://www.zapthedingbat.com/security/scriptinjection/%5B/url%5D

(this is not a browser vulnerability exploit, just bad site design practice)

nice! NOT!
here’s the most recent phishing scam which in essence exploits bad html design on the server, which allows cross site script injection (for instance mastercard.com is vulnerable)
http://www.zapthedingbat.com/security/scriptinjection/%5B/url%5D

(this is not a browser vulnerability exploit, just bad site design practice)

nice out-of-the-box thinking!

nice out-of-the-box thinking!