That very well may be.
The case here could be that there are different types of files visible in
the same workspace, and one uses "tbl" to differentiate tables from for
example stored procedures.
I don't know what kind of database is in question, but sometimes that
might be the only way to keep things logically organized.
P
> I'm guessing Mark's comment was about DB design, not query
> implementation, right? Otherwise, you would have to reference the
> actual table name when implementing your query.
>
> Jonathan
>
> Petri Laihonen wrote:
>
>>>Chris Reames wrote:
>>>
>>>
>>>>Select Democrats=(select count(voters) from tbl_state_list where vote
>>>>LIKE
>>>>'yes', Republicans=(select count(voters) from tbl_state_list where vote
>>>>LIKE
>>>>'no', Totals=(select count(voters) from tbl_state_list where vote is
>>>> not
>>>>null) from tbl_state_list where st_code='Florida'
>>>
>>>Since you aren't the first to do this, I'll ask: why include "tbl" in
>>>the name of a database table? Should we put "col" or "fld" in the names
>>>of the columns of the table? Or "db" in the name of the database we
>>>connect to?
>>>
>>>It seems redundant: why do it?
>>>
>>>
>>
>>
>> I suspect the table name IS "tbl_state_list"
>> Therefore can not be found with "state_list"
>>
>> Petri
>>
>> ___________________
>> Nolug mailing list
>> nolug@nolug.org
>>
> ___________________
> Nolug mailing list
> nolug@nolug.org
>
___________________
Nolug mailing list
nolug@nolug.org
Received on 09/29/04
This archive was generated by hypermail 2.2.0 : 12/19/08 EST