D
Dennis Allen
Hi. Have a problem, hope someone here could help. For years I've been
creating mail merge files from my Foxpro 2.6 applications. I simply create
a comma delimited file with record one containing field names. In switching
to Visual Foxpro, however, I have a problem with date columns.
A Foxpro 2.6 date field, such as 12/13/2003, is copied to the comma
delimited field in a ,20031231, format. With this format I can insert a
Word97 merge field like {if merge{dues}<20031231,"2003 dues past due",""}.
Well, Visual Foxpro creates date fields like ,12/31/2003,. The merge
{if}will print "2003 dues past due" because 12 is less than 20031231.
Question. Is there a way to test the value of ,12/31/2003, in a merge
field? Or is there a way to change the field value from ,12/13/2003, to
,20031231, so I can test the date?
Any help is appreciated...Dennis
creating mail merge files from my Foxpro 2.6 applications. I simply create
a comma delimited file with record one containing field names. In switching
to Visual Foxpro, however, I have a problem with date columns.
A Foxpro 2.6 date field, such as 12/13/2003, is copied to the comma
delimited field in a ,20031231, format. With this format I can insert a
Word97 merge field like {if merge{dues}<20031231,"2003 dues past due",""}.
Well, Visual Foxpro creates date fields like ,12/31/2003,. The merge
{if}will print "2003 dues past due" because 12 is less than 20031231.
Question. Is there a way to test the value of ,12/31/2003, in a merge
field? Or is there a way to change the field value from ,12/13/2003, to
,20031231, so I can test the date?
Any help is appreciated...Dennis