[AccessD] #Error

John,

Is the query you are building, or the subqueries, performing a calculation 
on the field in which you receive #error?

Thanks,

Mark A. Matte


>From: "JWColby" <jwcolby at colbyconsulting.com>
>Reply-To: Access Developers discussion and problem 
>solving<accessd at databaseadvisors.com>
>To: "'Access Developers discussion and problem 
>solving'"<accessd at databaseadvisors.com>
>Subject: [AccessD] #Error
>Date: Fri, 22 Dec 2006 11:09:30 -0500
>
>I am building up a query from subqueries.  One of the subqueries comes from
>a SQL Server view, linked to Access.  When I do an outer join on that
>subquery, I get #error in the fields for that subquery in any record where
>there is no data coming from the SQL Server linked table.
>
>Has anyone ever seen this before?  It looks similar to cases where you link
>to a spreadsheet and the data type changes down the table.
>
>It is ugly and I do not want to (can't really) send this out.  The end
>result will be a text file sent to a bank or insurance company for 
>automatic
>import into their database.  I have never found a way to turn that #error
>thing into any type of data that could be replaced with something else.
>
>John W. Colby
>Colby Consulting
>www.ColbyConsulting.com
>
>--
>AccessD mailing list
>AccessD at databaseadvisors.com
>http://databaseadvisors.com/mailman/listinfo/accessd
>Website: http://www.databaseadvisors.com

_________________________________________________________________
>From photos to predictions, The MSN Entertainment Guide to Golden Globes has 
it all. http://tv.msn.com/tv/globes2007/