250 fields in an access table

[soutie]

Hi guys,

I initially started with 19 fields in a table, now i have 250. I tried to split it into different tables and have struggled with updating, relations and so much more.

Can i just go ahead with 250 fields in a table? it makes my coding a lot easier. What are the risks? there will be on average 10 records for each field every month. I am just totally exhausted from working on this.

I know it should be in different tables etc, but my question is what if....

Cheers

[GaryMazzone]

The table can contain 250 fields yes. Should a table contain 250 fields no..... NO>>>NO.

Learn the right way to do things. If you don't learn at the begining then you will only have a much harder time later unlearning the stuff you did wrong.

[soutie]

thanks garymazzone, the thing is i wont ever be doing this again. im not a programmer but was asked by a friend to help out. So can i go ahead then?

[GaryMazzone]

You can do what ever you like. It is your application.

[soutie]

lol. What are the repercussions of doing it this way?

[GaryMazzone]

You get duplication of data, the app get slower.

[soutie]

thanks. The app will not have duplicates and there is only one user who will use it. Basically its like a large addressbook, each record is unique in that they will have around 250 fields such as colour, weight, dateofbirth and so on.

[RhinoBull]

Can i just go ahead with 250 fields in a table? it makes my coding a lot easier...

Sure, but it makes no sense either... You need to learn (if you want of course) basics of database design.
Link I provided is just of many-many on the internet - search further if article is difficult to understand.