Data not valid error message

  • Thread starter Thread starter NetworkTrade
  • Start date Start date
N

NetworkTrade

Access02

Have a Report which appears fine. But when you go from DesignView to
ReportView it throws error:
~.."the data you entered for this field is not valid"...

it doesn't say which field.....I can click thru the message and it reprompts
this a few times (probably once per instance of invalid) and then opens fine.

it does not do this when the Report opens ; only changing from design view...

but it does do it if it is multipage and you need to go to the next
page....so needs to be fixed...

there's alot of fields and so am wondering how to troubleshoot....hunch is
that it concerns fields that are comboboxes or possibly lookup fields where
possibly the bound column dataformat is causing this....
 
thank you for the link. I had search in the Reports area because mine is a
report and didn't search in the General area......

It confirms my hunch that the root cause of mismatch is probably lookup
field in underlying table. Because the bound column of the lookup is the
other table's key - which is a number; while the field is showing text.......
but on the otherhand this is a Report - not a Form - and was created via
Report Wizard.

everything I've done so far is very vanilla without customization.....
I'll modify the underlying query to link to the tables that have the text -
remove the numeric fields and add the text fields....

Seems like the product should either display the bound number values or
display the linked text and not throw errors - one or the other.... but to
display the text and then throw also an error is sort of like a football
player both committing the penalty and throwing the flag too....
 
I'll clarify the fix for anyone that might read this down the road.

The root cause was that a field in the underlying table had been changed
from a LookUp field to a plain old Text field in the table format.....after
this Report had been designed.

In Report's design view this field showed as a combobox still. If you
deleted it, and then put it back in from the field list - it was no longer a
combobox but was instead a regular text box. This was the fix.

To find a troublemaker control if you don't know which is the cause; delete
controls one at a time until the problem goes away. This identified the
trouble making control. You can delete a control, change to Report View - it
throws the error in this transition, return to DesignView - click the back
button which puts that deleted control back in place....and repeat this
process until the trouble control is found.....
 
Back
Top