If aceEntry.Name = "acheive" Then aceEntry.Delete When using Native Move the tool cannot merge into pre-existing objects Description When using Native Move the tool works fine with accounts which were mail enabled by the dirsync, but cannot work with accounts which already existed, or were created using different means. For more information, see Looping Through a Collection.
For example, the following deletes the AutoCorrect entry named "acheive" if it is part of the AutoCorrectEntries collection. If you are accessing a collection member by name, you can loop on the elements in a collection using a For Each.Next loop to determine if the named member is part of the collection. MsgBox "Document doesn't contain a table" The following example selects the first table, if there is at least one table in the active document. If you are accessing the member by index number, you can use the Countproperty of the collection to determine if the member exists. To avoid this error when accessing a member of a collection, ensure that the member exists prior to accessing the collection member. For example, the following instruction may post an error if the active document does not contain at least one table. The mail merge portion goes as follows: With docWord.MailMerge. The "requested member of the collection does not exist" error occurs when you try to access an object that does not exist. About six months ago, I created a function in Access 2002 that would perform a mail merge based on a template file in Word.