Maximum number fields in Access 2000 table

[Larry Spitz]

Ias there a maximum number of fields for a table in Access
2000.

 

[Kevin3NF]

255. If you get even close to that, you may want to re-think your database
design.

--
Kevin Hill
President
3NF Consulting

www.3nf-inc.com/NewsGroups.htm

 

[Guest]

I am designing an Appointment Book for a small business. If I make a table the obvious way I end up with 460 fields. Any thing out there on this subject? Any suggestions?

 

[Kevin3NF]

Normalize the data? Not sure what the obvious way is...

--
Kevin Hill
President
3NF Consulting

www.3nf-inc.com/NewsGroups.htm

I am designing an Appointment Book for a small business. If I make a table

the obvious way I end up with 460 fields. Any thing out there on this
subject? Any suggestions?

 

[John Vinson]

I am designing an Appointment Book for a small business. If I make a table the obvious way I end up with 460 fields. Any thing out there on this subject? Any suggestions?

Well, in this case, the "obvious" way is clearly not properly
normalized. I've needed as many as sixty fields in a table, once or
twice in the past two decades. Surely you're embedding some sort of a
one-to-many relationship within this monster!

What kind of data make up these 460 fields? (Don't give an
exahaust(ive)(ing) list please...)

 

[Guest]

The person I am doing this for requires spaces for a weeks table with 3 spaces per day and 24 entries per each. His week is 6 days. So we have 6daysX3 entries per day and one entry for every half hour with a 12 hour day.
I keep thinking that there has to be a simple answer not this obvious answer I keep coming up with. I am stuck in a rut. Need some fresh thinking
There are a lot of businesses that are using appointment schedules. What time are the live chats?

----- John Vinson wrote: -----

I am designing an Appointment Book for a small business. If I make a table the obvious way I end up with 460 fields. Any thing out there on this subject? Any suggestions?

Well, in this case, the "obvious" way is clearly not properly
normalized. I've needed as many as sixty fields in a table, once or
twice in the past two decades. Surely you're embedding some sort of a
one-to-many relationship within this monster!

What kind of data make up these 460 fields? (Don't give an
exahaust(ive)(ing) list please...)

 

[Tim Ferguson]

Any suggestions?

MS Outlook, Act!, Lotus something, Groupwise, Palm Datebook...

Web based; PDA based; graphical- or character-based; diaries for the blind;
diaries for the deaf; ones that link with your phone book, ones that will
dial the phone itself; schedulers with built in billing, or ones that buy
your wife flowers on her birthday. Have you looked in WinFiles.com?

The biggest advantage, of course, in using a professionally written program
is, when it goes wrong, you can sue the company that sold it. If you write
something and your boss loses money because it doesn't work, all he can do
is break your legs and sack you.

Just 2p worth..


All the best



Tim F

 

[TC]

You need to read:

http://support.microsoft.com/support/kb/articles/Q100139.ASP

HTH,
TC

The person I am doing this for requires spaces for a weeks table with 3

spaces per day and 24 entries per each. His week is 6 days. So we have
6daysX3 entries per day and one entry for every half hour with a 12 hour
day.

I keep thinking that there has to be a simple answer not this obvious

answer I keep coming up with. I am stuck in a rut. Need some fresh thinking

There are a lot of businesses that are using appointment schedules. What time are the live chats?

----- John Vinson wrote: -----

table the obvious way I end up with 460 fields. Any thing out there on this
subject? Any suggestions?

 

[Guest]

The Obvious way to me anyway is to provide a dedicated field for each day of the week, each 1/2 hour of the day and 3 entries per every half hour. This is what makes the overrun in field requirements

----- Kevin3NF wrote: ----

Normalize the data? Not sure what the obvious way is..

--
Kevin Hil
Presiden
3NF Consultin

www.3nf-inc.com/NewsGroups.ht

I am designing an Appointment Book for a small business. If I make a tabl

the obvious way I end up with 460 fields. Any thing out there on thi
subject? Any suggestions