B
Bod
I am using a SQL Server View (combining fields from 3 tables) as the data
source for a Mailmerge. If a field is defined as nvarchar in the SQL table
it does not appear in the merged document, but if the definition is changed
to varchar it merges correctly. Why is this?
Also a field defined as datetime in the SQL table refuses to accept format
switches -
{MERGEFIELD Tx_Date \@ "dd/mm/yyyy"}
{MERGEFIELD Tx_Date \@ "yyyy.mm.dd"} etc...
Always appears in the document as
04/12/2004 00:00:00
Why is this?
(I'm using Office XP (Word 2002) and SQL Server 2000 if that matters)
Cheers
source for a Mailmerge. If a field is defined as nvarchar in the SQL table
it does not appear in the merged document, but if the definition is changed
to varchar it merges correctly. Why is this?
Also a field defined as datetime in the SQL table refuses to accept format
switches -
{MERGEFIELD Tx_Date \@ "dd/mm/yyyy"}
{MERGEFIELD Tx_Date \@ "yyyy.mm.dd"} etc...
Always appears in the document as
04/12/2004 00:00:00
Why is this?
(I'm using Office XP (Word 2002) and SQL Server 2000 if that matters)
Cheers