Hi Tasha,
And your question is?<g>
This sort of thing sometimes happens if there's a text value in Access
that Excel assumes is a number or a date. If it's never happened before
and is happening now, something has changed, in your Microsoft Office
setup, your database, or your data.
One approach that usually the problem is to prefix the field values in
question with an apostrophe: this forces Excel to treat thenm as text.
If you post back with some examples of the exact values that are
displayed in the report when previewed, and the corresponding values
displayed by Excel after export, someone may be able to make a better
suggestion.
>A report I use to export to excel from Access using "DoCmd.OutputTo acReport,
>ReportName" is now providing me with different values. Data like 12-1369 is
>returning a value of -193607. Note: not all the values are changed. It is
>very inconsistent. Thanks!
--
John Nurick [Microsoft Access MVP]
Please respond in the newgroup and not by email.
John, I'm sorry but I'm not seeing your reply.
thanks!
> A report I use to export to excel from Access using "DoCmd.OutputTo acReport,
> ReportName" is now providing me with different values. Data like 12-1369 is
> returning a value of -193607. Note: not all the values are changed. It is
> very inconsistent. Thanks!
John Nurick - 30 Jun 2006 21:37 GMT
Here it is again:
This sort of thing sometimes happens if there's a text value in Access
that Excel assumes is a number or a date. If it's never happened before
and is happening now, something has changed, in your Microsoft Office
setup, your database, or your data.
One approach that usually the problem is to prefix the field values in
question with an apostrophe: this forces Excel to treat thenm as text.
If you post back with some examples of the exact values that are
displayed in the report when previewed, and the corresponding values
displayed by Excel after export, someone may be able to make a better
suggestion.
>John, I'm sorry but I'm not seeing your reply.
>
[quoted text clipped - 4 lines]
>> returning a value of -193607. Note: not all the values are changed. It is
>> very inconsistent. Thanks!
--
John Nurick [Microsoft Access MVP]
Please respond in the newgroup and not by email.