AHHHHHHH!
I have just discovered a very annoying problem.
I have a quite complicated system set up in office 2000 using access to run mail merges. In Word 2000, if a date field in the database is blank, then the merge field is blank (sounds sensible to me). I then have IF fields which ensure the letter makes sense if the field is blank.
BUT
I have a new user who is running Word 2002. On her machine, if a date field is blank in the database, the mergefield linked to that blank field will instead insert today's date. Hence all my lovingly created IF fields checking to see if the date is blank or not do not work and letters are produced that don't make sense.
I have trawled through Word help but can find nothing about this - I really hope that there is an option about this that I am missing, if not, can anybody suggest anything?
Many thanks for any help that you can give
I have just discovered a very annoying problem.
I have a quite complicated system set up in office 2000 using access to run mail merges. In Word 2000, if a date field in the database is blank, then the merge field is blank (sounds sensible to me). I then have IF fields which ensure the letter makes sense if the field is blank.
BUT
I have a new user who is running Word 2002. On her machine, if a date field is blank in the database, the mergefield linked to that blank field will instead insert today's date. Hence all my lovingly created IF fields checking to see if the date is blank or not do not work and letters are produced that don't make sense.
I have trawled through Word help but can find nothing about this - I really hope that there is an option about this that I am missing, if not, can anybody suggest anything?
Many thanks for any help that you can give