>>I was doing SQL like select * from Table1 inner join table2 etc. Tables have the same fieldnames. Usually SQL renames field to field_a, field_b, etc. Some field names were 10 symbols long. SQL does something strange: in same cases it adds _a prefix and in some - adds 2 at the end? Does somebody see this behavior and have explanations? Moreover, how many fields can this free table contain? If I select 100 fields from Table1, 100 from Table2, 100 from Table3, etc., will it error and what error it would be?
>

---

>
>Just a gotcha I'd like to point out: should you move your data to another backend, you can't assume the other backend will name the duplicate field name the same way VFP does. SQLServer, for example, doesn't follow VFP's example.
>
>I think you should always name each of your fields. I know, it can be very long sometimes when you have lots of fields, but I think it might prevent a few problems along the way.
>
>Besides, you can write a little PRG which will use AFIELDS to list all the fields in your current work area, so issue your initial SELECT - SQL, use that PRG to put the field list in the _CLIPTEXT, paste in your code and make the modifications you require.
>
>Just my 2 cents...

Hi Sylvain,

I knew, somebody would advise it :) Well, we have join 5 tables, each of them has ~40-60 fields, so it would be really tough to name them all. Do you know, how SQL handles the same field name? And Oracle? Currently we use VFP native tables and I'm not sure, we're going to switch soon, but who knows...