Hi Ken ----

Hmmm...and you use INNER/OUTER JOINs? On remote and local data? BTW, your naming convention was really common in the old days of ISAM tables and still is useful.


>FYI - ALL my fields are named with underscores because I use the naming convention of xx_name where xx is a table designator ie. cs_phone would be my customer phone number field. I am completely sold on this convention as it has many advantages including not having to specify table/alias in SQL statements and always knowing at a glance which "phone number" or whatever you're dealing with. I Know many will disagree with this and most ER tools seem to not like it - but hey, I view that as THEIR problem, not mine.
>
>Anyway - my real point is, in answer to your question, that I've been doing this in all my apps in all versions of Fox/VFP for years - including lots of views - and never had a problem with SQL and the underscores.
>
>Good Luck ...
>
>
>>Hi All ---
>>
>>Was running a simple outer join against two remote views (SQL Server) in VFP6. Kept getting "Column action_ID" not found for one of the tables (which is bogus). Changed the view definition so that the field name is "actionid" in the remote view, everything works.
>>
>>Went back to some old VFP3 notes and found that I had the same problem way back when with SELECT statements using the JOIN keyword and fields with underlines in them whether or not local or remote views.
>>
>>Anyone else ever run into this or could shed some light on this?