>Trey:
>It's a very conventional select statement - just "select field1, field2 FROM table WHERE ..." etc., and uses an established VFP remote view connection link that has been used successfully in every other related query for a long time. I'm wondering if, like ACCESS (sorry to even mention that name here) there may be a problem with recognizing certain hieroglyphics contained ion the character string but that has not been a problem before in VFP. So I keep wondering whta is wrong this time???
>
>Thnx for your input. /psb

I doubt either the connection itself or the non-alphanumeric string is causing any problems - like you said, they've worked in the past.

I think the problem may be in how the view is getting called.
Are there view parameters in your view's where clause? In the select from your original post, you mentioned this select:

SELECT bc.* FROM babychg_basic_view1 bc ;
   WHERE bc.pat_id = ?pat_id and bc.hosp_id = ?hosp_id

A parameterized view would have a where clause like that- i.e., where column = ?variable .... Using column = ?variable outside of a view definition is the same as using column = variable. If the variable exists, the "?" won't error; if the variable doesn't exist, it will. Not sure why: I'd think it should either error whether or not the var exists, or prompt if it doesn't, like in a view.

If these parameters aren't in the view, then the view itself will return all the rows matching its criteria prior to the VFP sql-select being fired.