Prev: How to update data in a query
Next: Nested JOIN clauses - order of precedence (Access 2007)
From: sexybrown28 on 5 Apr 2010 17:38

From: Jeff Boyce on 5 Apr 2010 18:16
Not sure I understand what you are trying to do.

Have you tried adding Option Explicit to the top of all of your code
modules? This will force you/the developer into defining (i.e. DIM-ing) all
variables, and may help identify how the mismatch is happening.

Regards

Jeff Boyce
Microsoft Access MVP

--
Disclaimer: This author may have received products and services mentioned
in this post. Mention and/or description of a product or service herein
does not constitute endorsement thereof.

Any code or pseudocode included in this post is offered "as is", with no
guarantee as to suitability.

You can thank the FTC of the USA for making this disclaimer
possible/necessary.

"sexybrown28" <sexybrown28(a)discussions.microsoft.com> wrote in message
news:09B900BC-909D-4D21-AFAE-487211486DCB(a)microsoft.com...
>


From: John W. Vinson on 5 Apr 2010 22:43
On Mon, 5 Apr 2010 14:38:34 -0700, sexybrown28
<sexybrown28(a)discussions.microsoft.com> wrote:

By correcting the error in the expression so it doesn't try to store one type
of data into a different type of field.

If you would like help doing so, please post the expression and indicate the
relevant datatypes. We can't see your computer screen from here!
--

John W. Vinson [MVP]
 | 
Pages: 1
Prev: How to update data in a query
Next: Nested JOIN clauses - order of precedence (Access 2007)