Re: Will ASP query be slow if field names are lengthy?

Tech Tip: Click here to run a free scan for Windows Errors and optimize PC performance

From: Evertjan. (exjxw.hannivoort_at_interxnl.net)
Date: 12/07/04 

Date: 07 Dec 2004 09:47:44 GMT

Lasse Edsvik wrote on 07 dec 2004 in
microsoft.public.inetserver.asp.general:

> Its a very bad idea to add extra columns just for description, Just
> create a readme.txt instead were you describe your tables. Else you'll
> end up with a really big database with unnecessary information.
>
> columns, not fields.....
>
> Never list more than 100 in a page...... use paging if needed......
> and if your database is going to be that large you might consider
> using SQL Server instead.
>
> "ynott" <ynott@hotmail.com> wrote in message
> news:77mar0d4fg1gvuttnbubpeojmle861gf88@4ax.com...
>> I have an Access database with 58 fields in one table. I wrote many
>> of the field names so that they were descriptive so that others could
>> figure it out in the future. As an example, one field name is called
>> MissingPart14990aDescribe.
>>
>> Should I be worried about the length of the field name? I'm
>> expecting about 20,000 records a year to be entered into the
>> database. So, five years from now, which would be about 100,000
>> records, will the query.asp for a list of records be slow due to
>> field name size? BTW, the query.asp would just show a list of the
>> last 3 months worth of records and only a snapshot of about 6 of the
>> 58 fields.

[This is what happens with topposting:

ununderstandable answers, because you have to scroll down for the
individual questions again and again.

Please use interposting on usenet.]

Records have fields, HTMLtables have rows and columns, Database tables
are a random collection of records, and because of the randomness the
records shouldn't be called rows. 

-- 
Evertjan.
The Netherlands.
(Replace all crosses with dots in my emailaddress)