M
Mike375
Guest
The code I have for the Word.docs was done by the Access developer company and because the code I used in Access 95 would not work in A2003. The problem was EditGoTo for the Bookmarks would not work. I contacted Microsoft and they confirmed that EditGoTo was a problem and then gave me the name of the Access Developer company.
docmd.domenuitem would be a conversion of a macro where the macro was made in A95.
The biggest mistake I made was letting the Access developer go his own way....which resulted in a huge module (another one). The stuff is also linked to a form name and can't be used elswhere. The fact that I can do a work around to open Word.docs and Bookmarks etc on another form is besides the point. What has me beat is why they do so much typing. What I did in A95 was each label that held the code was independent and I had one lot of typing....then copy/paste and simply change the Word.doc name.
So far there have only been the two failures. We always go back after the print is done and check the letter has been copied to a new Access record. I don't know if the huge module is a problem or A2003 or XP as we never had a failure on A95 and Windows 98. The two failures were no big deal because it worked on third attempt and there were no failures before and no failures since.
But I have seen the same with macros. In my opinion if someone thinks code or macros are 100% then they are wrong. But perhaps because my data base has so many loop around, open form, close form etc and etc all off one click it may cause a problem. I have never claimed this data base is an example of fine engineers at work
docmd.domenuitem would be a conversion of a macro where the macro was made in A95.
The biggest mistake I made was letting the Access developer go his own way....which resulted in a huge module (another one). The stuff is also linked to a form name and can't be used elswhere. The fact that I can do a work around to open Word.docs and Bookmarks etc on another form is besides the point. What has me beat is why they do so much typing. What I did in A95 was each label that held the code was independent and I had one lot of typing....then copy/paste and simply change the Word.doc name.
So far there have only been the two failures. We always go back after the print is done and check the letter has been copied to a new Access record. I don't know if the huge module is a problem or A2003 or XP as we never had a failure on A95 and Windows 98. The two failures were no big deal because it worked on third attempt and there were no failures before and no failures since.
But I have seen the same with macros. In my opinion if someone thinks code or macros are 100% then they are wrong. But perhaps because my data base has so many loop around, open form, close form etc and etc all off one click it may cause a problem. I have never claimed this data base is an example of fine engineers at work