D
Doogle
I've been having a great deal of fun (or not...) programming a Word doc from
within an Access VBA module to go as an email attachment (hello Outlook - and
Outlook Redemption), with an Excel attachment as well (it's all there,
folks!). The objective is to mail about 800 companies on my client's database
system, showing them the data we hold on them and asking them to update &
return the attachments so my client's staff can then update the database
itself. Office 2003 on a Windows 2000 Pro/Windows 2000 Server network.
What a great oppportunity for a doc with form-fields and 'Tracking Changes',
I hear you all cry. As did I. And boy have I been crying!!
Why? Well, firstly it took me ages to discover that even if you 'accept all
changes' etc, saving the file as an RTF is not clever - it insists on
displaying all the changes. So, save as a DOC. Great!! And turn off
'balloons' so their own changes don't frighten the clients too much.
BUT HERE'S THE QUESTION (yes, at last...). A substantial number of the
fields in the database for inclusion in the word doc (roughly 70 out of some
110) are simple yes/no fields - welcome to the 'checkbox' category of
'formfields'. Nice and easy to program. But -
*** WHY DOESN'T CHANGING A CHECKBOX FROM TRUE TO FALSE (OR FALSE TO TRUE)
REVEAL ITSELF AS A 'TRACKED CHANGE'??***
Or is there something I've missed? OK, there are workarounds (program them
as text fields with 'Yes' or 'No', or maybe as text fields with 'X' or
nothing - changes in either of these would register) but I'd prefer the
'elegance' of the checkbox if it can be forced to behave properly.
Maybe next year I'll have persuaded them that I should set it up as an ASP
solution on the net. Hey-ho!!
Comments please - PLEASE!!!
within an Access VBA module to go as an email attachment (hello Outlook - and
Outlook Redemption), with an Excel attachment as well (it's all there,
folks!). The objective is to mail about 800 companies on my client's database
system, showing them the data we hold on them and asking them to update &
return the attachments so my client's staff can then update the database
itself. Office 2003 on a Windows 2000 Pro/Windows 2000 Server network.
What a great oppportunity for a doc with form-fields and 'Tracking Changes',
I hear you all cry. As did I. And boy have I been crying!!
Why? Well, firstly it took me ages to discover that even if you 'accept all
changes' etc, saving the file as an RTF is not clever - it insists on
displaying all the changes. So, save as a DOC. Great!! And turn off
'balloons' so their own changes don't frighten the clients too much.
BUT HERE'S THE QUESTION (yes, at last...). A substantial number of the
fields in the database for inclusion in the word doc (roughly 70 out of some
110) are simple yes/no fields - welcome to the 'checkbox' category of
'formfields'. Nice and easy to program. But -
*** WHY DOESN'T CHANGING A CHECKBOX FROM TRUE TO FALSE (OR FALSE TO TRUE)
REVEAL ITSELF AS A 'TRACKED CHANGE'??***
Or is there something I've missed? OK, there are workarounds (program them
as text fields with 'Yes' or 'No', or maybe as text fields with 'X' or
nothing - changes in either of these would register) but I'd prefer the
'elegance' of the checkbox if it can be forced to behave properly.
Maybe next year I'll have persuaded them that I should set it up as an ASP
solution on the net. Hey-ho!!
Comments please - PLEASE!!!