![]() | |
![]() |
| | Thread Tools | Display Modes |
#1
| |||
| |||
|
#2
| |||
| |||
|
|
I have an mde written in Access 97, converted to A2000, and used by all flavours of Access from 97 to 2010. One of the reports includes code to change the colour of one field from black to red, by setting the ForeColor property of the report field when the report opens. * * * * If Forms![SetupF]![ColourReminders] = True Then * * * * * * If [DocumentType] Like "*Reminder*" Then * * * * * * * * [OverdueMessage].ForeColor = 255 * * * * * * End If * * * * End If This works fine on the preview, and usually on the printout. However, some clients find that the printed report either prints the red field in black, or a variant of colour that is not red. This is despite the printer printing colour perfectly well from other applications. Reinstalling the printer driver does not help. Any suggestions? Owen |
#3
| |||
| |||
|
|
I have an mde written in Access 97, converted to A2000, and used by all flavours of Access from 97 to 2010. One of the reports includes code to change the colour of one field from black to red, by setting the ForeColor property of the report field when the report opens. * * * * If Forms![SetupF]![ColourReminders] = True Then * * * * * * If [DocumentType] Like "*Reminder*" Then * * * * * * * * [OverdueMessage].ForeColor = 255 * * * * * * End If * * * * End If This works fine on the preview, and usually on the printout. However, some clients find that the printed report either prints the red field in black, or a variant of colour that is not red. This is despite the printer printing colour perfectly well from other applications. Reinstalling the printer driver does not help. Any suggestions? Owen Would it not be better to write: |
#4
| |||
| |||
|
#5
| |||
| |||
|
|
Hi Jim, Thanks, I guess so, but RGB(255,0,0) evaluates to 255 anyway, and makes no difference to this problem. Owen |
#6
| |||
| |||
|
![]() |
| Thread Tools | |
| Display Modes | |
| |