Dlookup form printing problems - strange behavior

[Guest]

I am having some strange problems with Dlookups on my form. I have a form
backed by a query. On the form I have a few combo boxes and calculated
fields. I then have some text boxes (unbound) where I am placing my Dlookup
statements.
I am asking the Dlookup to find a value ([ColorName]) in one column on a
query ([Customer Color Query]) where a value on my form ([CONCAT1]) = a value
in another column ([CONCAT])on the same query. I have 12 text boxes with
Dlookup statements total. I KNOW my syntax is correct - I've seen the
multiple posts on multiple sites in multiple forums showing me what syntax to
use when using criteria that is either a date, text, or a number. In my case
it's all text so i'm using the "[My Field] = ' " & [My Other Field] & " ' "
syntax for my criteria.

So here's the weird thing....
In my 12 Dlookup statements, I get them all to "work" - they pull the value
I want off the query. However, when I go to print preview the form with all
the Dlookups on it, some fields maintain the value they've pulled, some
change to #Name?. When the form prints, it does this as well. I can't
figure this out. Anyone have any ideas? I can post more info if required.
Oh yes, I have Access 2002 newly installed on my machine. Do I need Office XP
service pack 3 to fix my problems? The office update site says I need SP3, I
just don't know if that will fix my issue or not.

Thanks for your help,
-Chris

 

[Guest]

To anyone wanting to respond to my earlier post, here's some more info.
After carefully checking my syntax on all my Dlookups, all seems fine as I
originally thought. When going into print preview while on the form itself,
I still get the #Name? error in some of my Dlookup fields while other Dlookup
fields show as normal (I'm getting 3 out of the 12 show as normal, the other
9 are showing up #Name?).

The new info I am posting here is that when I go into print preview on the
form from the database window, the form print previews as normal - all
Dlookups show correctly.

this seems like some kind of access flaw of some kind. no? if anyone has
any insight that would be great.

thanks,
Chris