JWColby
jwcolby at colbyconsulting.com
Fri Dec 22 11:35:29 CST 2006
In fact I am doing this. John W. Colby Colby Consulting www.ColbyConsulting.com -----Original Message----- From: accessd-bounces at databaseadvisors.com [mailto:accessd-bounces at databaseadvisors.com] On Behalf Of Dan Waters Sent: Friday, December 22, 2006 11:25 AM To: 'Access Developers discussion and problem solving' Subject: Re: [AccessD] #Error Could you first create a query for the SQL Server linked table which will only select record with data? Then do the outer join? Dan Waters -----Original Message----- From: accessd-bounces at databaseadvisors.com [mailto:accessd-bounces at databaseadvisors.com] On Behalf Of JWColby Sent: Friday, December 22, 2006 10:10 AM To: 'Access Developers discussion and problem solving' Subject: [AccessD] #Error 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 -- AccessD mailing list AccessD at databaseadvisors.com http://databaseadvisors.com/mailman/listinfo/accessd Website: http://www.databaseadvisors.com