Duane Hookum

G

Guest

I have been reading your responses and think you may be able to help me. I
had a query & form based on a table and a report from the query. The table
had Lookup fields. I changed the lookup fields to text and modified my form
to include lookup fields. The table, query and form are all working fine.
However, my report gives me an error message: "The value you entered isn't
valid for this field." I have checked all the settings and everything
appears fine. I can even create a new report on this same query and it runs
fine. I have even deleted the field from my report and still get the error
message. I think it has something to do with using the Rpt Wizzard and
something in the background that I can't see. I can create a new report but
have spent much time designing this one. Can you help with this one?
Thanks!
 
D

Duane Hookom

The error message doesn't provide much help. I would check the sorting and
grouping for unknown fields. Also check control sources for missing field
names.

Your statement "I changed the lookup fields to text" scares me. I'm not sure
why you would change a data type. Removing a lookup defined in a table
doesn't generally mean that you would change a field type. You should be
storing the primary key value from a related "lookup" table. This should be
implemented in a form rather than a table.
 
G

Guest

I changed the table after realizing that the Lookup should be in my form.
When changing the field from lookup to not lookup it changed to text. If I
try to change the type of the field now it says I will loose data. The
table, query, and form all work fine. I can create a new report on this
query and it works. There is just somehting in this report that will not. I
can view the report afte hitting enter several times. I have checked the
group/sort, control, etc. Even deleting the field from the report doesn't
fix it.
 
D

Duane Hookom

Do you have any subreports in your report? Are there any combo box or list
box controls on your report?
 
G

Guest

No. The report was created by using the Wizzard with groupings for Send to;
Date; Wire# and summed on the Send to. The Wire# field is the problem.
Again, the only problem is in the orginal report as everything else works
perfectly. Even this field shows-up fine when the report finally opens.
Thanks!
 
D

Duane Hookom

I would make a copy of the report and then begin removing controls one at a
time to check for errors.
 
G

Guest

Thank you for your help. Taking your last advice, I began looking at
controls in other fields. It wasn't in the Wire # (don't even remember why I
though that was the problem!) but was in what had previously been lookup
fields. Changing them in the table effected the query and I manually changed
them in the form but needed to also manually change the control in the
report. Now it works!
 
D

Duane Hookom

That's kinda why I posted "Your statement "I changed the lookup fields to
text" scares me". I should have been more specific.

Glad to hear you got this sorted out.
 

Ask a Question

Want to reply to this thread or ask your own question?

You'll need to choose a username for the site, which only take a couple of moments. After that, you can post your question and our members will help you out.

Ask a Question

Top