Wrox Programmer Forums

Need to download code?

View our list of code downloads.

| FAQ | Members List | Calendar | Search | Today's Posts | Mark Forums Read
ASP.NET 1.0 and 1.1 Basics ASP.NET discussion for users new to coding in ASP.NET 1.0 or 1.1. NOT for the older "classic" ASP 3 or the newer ASP.NET 2.0.
Welcome to the p2p.wrox.com Forums.

You are currently viewing the ASP.NET 1.0 and 1.1 Basics section of the Wrox Programmer to Programmer discussions. This is a community of tens of thousands of software programmers and website developers including Wrox book authors and readers. As a guest, you can read any forum posting. By joining today you can post your own programming questions, respond to other developers’ questions, and eliminate the ads that are displayed to guests. Registration is fast, simple and absolutely free .
DRM-free e-books 300x50
Thread Tools Search this Thread Display Modes
  #1 (permalink)  
Old January 24th, 2006, 05:59 AM
Friend of Wrox
Join Date: May 2005
Location: , , .
Posts: 149
Thanks: 0
Thanked 0 Times in 0 Posts
Default access table

I want to design an application.The database is ms access.
I have a table that has about 40 fields.
Regarding performance issues I want to know is it better to use one table or to use multiple tables and join them sql command through a unique ID?

  #2 (permalink)  
Old January 24th, 2006, 02:49 PM
Friend of Wrox
Points: 4,332, Level: 27
Points: 4,332, Level: 27 Points: 4,332, Level: 27 Points: 4,332, Level: 27
Activity: 0%
Activity: 0% Activity: 0% Activity: 0%
Join Date: Nov 2003
Location: , NJ, USA.
Posts: 1,348
Thanks: 0
Thanked 5 Times in 5 Posts

First I would suggest using SQL Express. It is a chopped down version of SQL Server 2005. It's free and is a true relational database. No matter what DB you use, you should design it so that it is relational. Then you can access your data using JOIN conditions.


  #3 (permalink)  
Old January 24th, 2006, 03:22 PM
planoie's Avatar
Friend of Wrox
Points: 16,481, Level: 55
Points: 16,481, Level: 55 Points: 16,481, Level: 55 Points: 16,481, Level: 55
Activity: 0%
Activity: 0% Activity: 0% Activity: 0%
Join Date: Aug 2003
Location: Clifton Park, New York, USA.
Posts: 5,407
Thanks: 0
Thanked 16 Times in 16 Posts

You don't necessarily need to break apart the table, however it might make logical sense to. You could create a second table for fields that belongs together but that doesn't necessarily have to live with the first set of fields.

One thing to consider: are there certain fields that would be accessed a lot while others would not be? If so, then you might benefit from putting less-used fields in another table with a one-to-one relationship to the rows in the "master" table.


Thread Tools Search this Thread
Search this Thread:

Advanced Search
Display Modes

Posting Rules
You may not post new threads
You may not post replies
You may not post attachments
You may not edit your posts

BB code is On
Smilies are On
[IMG] code is Off
HTML code is Off
Trackbacks are Off
Pingbacks are On
Refbacks are Off

Similar Threads
Thread Thread Starter Forum Replies Last Post
Create new Table in access djobes31770 VB Databases Basics 4 November 20th, 2007 09:37 AM
Photo in Access table mateenmohd Access 2 November 2nd, 2007 08:48 AM
Access Table Records TonyG Access 7 October 14th, 2005 02:32 AM
Update an access table Rash4u Classic ASP Databases 2 February 3rd, 2005 04:24 PM

All times are GMT -4. The time now is 02:01 PM.

Powered by vBulletin®
Copyright ©2000 - 2019, Jelsoft Enterprises Ltd.
© 2013 John Wiley & Sons, Inc.