>>Is there a way (other than trial and error) to determine which column/field is the problem? There are over 120 columns in this particular view, although only 3 are memo fields (which *must* translate to varchar). Thanks for the input.
>>

As it turned out, the problem was not with any of the columns in the remote view, but in the "Advanced Options" which alter the SQL connection parameters. I changed the BatchUpdateCount from 5 to 1, and de-selected "Precompile SQL on backend server" and voila! it started working!

Isn't it a little bizarre that I got the 'numeric overflow' error message? Any logical explanation, or is this another attack of the 'random error message generator engine' in ODBC?


>
>There's no easy way that I know of. If you open the view in the designer, on the fields page there's a Properties button which will show you the properties for the field selected in the listbox on the left.
>
>The only other course of action would be to systematically remove columns until the problem stops.

Fortunately I didn't have to resort to this. It occurred to me that I could probably run GENDBC against the remote view, then peruse the output file for data typing mistakes. I have a "hacked" version that operates on one view at a time, rather than the entire DBC. I think I have seen an identical utility posted here on UT.

Thanks for your suggestions!

>
>-Mike