>>>Antonio:
>>>
>>>(Advice to EVERYONE as well)
>>>
>>>The other responses to your question should be of some help. My advice, however, has to do with your use of the field name "number". If this is just an example (i.e., not the real field name), please disregard this response. Otherwise, change the field name as soon as you can. Names like NUMBER, DESC (for a description), TYPE, TOTAL, etc., are reserved by any or all software such as FoxPro, Oracle, Access, etc. We had one "rocket scientist" here that had an Oracle column name as "NUMBER" and it caused all kinds of problems with SQL. I could tell your use of "quantity" and "value" were just examples but not as sure about the "number".
>>>
>>
>>As far as NUMBER, TYPE, TOTAL are concerned, its ok. But Desc is also
>>problem ?? as I am using it in my 3-4 dbf's in diff. projects.
>>
>>Pls advs.
>
>Vinod, DESC is interpreted as "Descending" and causes VERY unpredictable results in SQL. However, if you ARE using it in existing tables, just be sure you preface it with the alias (MyTable.Desc) and you should be OK. If you've been careful to use this syntax all along, you probably haven't had any trouble.
>
>HTH
>Barbara

Thanks, this clears the thing. Actually I don't remember what exactly I did, because I have used it in more then 3-4 projects.

I won't take chances and change the name. Thanks again !!