Pardon me, but have you considered giving up app-generated code and actually learning T-SQL?
That "NULL IS NOT NULL" stuff is pure bovine excrement.
< M!ke >
Electile dysfunction: the inability to become aroused over the choices put forth by either party for an election year.
How about
User: Why...
Me: Because Microsoft...
That's usually enough.
< M!ke >
Electile dysfunction: the inability to become aroused over the choices put forth by either party for an election year.
Yeah, but you'd have to have it on your front bumper and reversed so it could be read in the ID10T's rear-view mirror...
And that's asking a lot given the lack of intelligence of all those OTHER drivers!
< M!ke >
Where are we going and why am I in this handbasket?
Okay - understanding the operative word is "legal" can you give any specific examples of the situation? Data types and values on the back end and what the incorrectly displaying data is on the front end?
Also, what version of SQL Server?
I know from past experience that the slight variations...
First off, Access 2000 didn't come out in 1996 (sorry, I couldn't resist).
You say that
and then you talk about the problem residing with an Access front end reference (forms![dataform]!CustomerCode).
I'd suspect the issue is in the form's property setting; not the back end data.
You might...
Seems like this question would be better answered here:
http://www.tek-tips.com/threadminder.cfm?pid=717
< M!ke >
Where are we going and why am I in this handbasket?
This site uses cookies to help personalise content, tailor your experience and to keep you logged in if you register.
By continuing to use this site, you are consenting to our use of cookies.