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

From: Lasse Edsvik (lasse_at_nospam.com)
Date: 12/07/04

  • Next message: Pedram Rahimi: "Write Farsi ( Persian ) in Access by Web form"
    Date: Tue, 7 Dec 2004 10:21:35 +0100
    
    

    ynott,

    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.

    /Lasse

    "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.
    >
    > TIA


  • Next message: Pedram Rahimi: "Write Farsi ( Persian ) in Access by Web form"

    Relevant Pages

    • Possible ways to link existing user table into SQLMembershipProvider?
      ... I have membership working well and I'm trying to integrate it into a ... database that makes heavy use of a pre-existing 'User' table. ... table with a few extra columns and a 'loginname' column to join back to ...
      (microsoft.public.dotnet.framework.aspnet.security)
    • Re: Create Indexes & extra columns!
      ... > I have not yet had the guts to do it while the database was in use ... index is a more time consuming process if the table is large. ... create a clustered index, you'll likely take the table offline until the ...
      (microsoft.public.sqlserver.server)
    • Create Indexes & extra columns!
      ... I have not yet had the guts to do it while the database was in use however ... Regards ...
      (microsoft.public.sqlserver.server)
    • Re: Three Basic Questions about Developing a Runtime Version of Access
      ... Is it worth the effort to distribute a run-time version of an Access ... The 2nd database should have table links to the database ... data to a new data file containing the new tables/fields. ...
      (microsoft.public.access.devtoolkits)
    • Re: Removing datasets from our architecture...
      ... If that's true it might be worth the cost to make a change. ... Depending on how you built your app you may need to merely create a new database and change the connection string you are using to connect to the DB. ... I guess the existing code works, but its close to unmaintainable, so I wonder weather now is the time to jump ship to proper business objects instead of trying to hack around with datasets... ... "Andrew Faust" wrote in message ...
      (microsoft.public.dotnet.general)