How to bypass 32 index restriction

[Jana]

I am building a huge relational database in ACCESS 2003. I have created 302
tables, all extremely large. These are all necessary, and because of my job
I must create an ACCESS database so that it can be eventually posted online
and collect data via forms. Please, I beg anyone, is there a way to get
around this restriction? I'm desperate, so I welcome ANY suggestions. Thanks!

 

[pietlinden]

I am building a huge relational database in ACCESS 2003. I have created 302
tables, all extremely large. These are all necessary, and because of my job
I must create an ACCESS database so that it can be eventually posted online
and collect data via forms. Please, I beg anyone, is there a way to get
around this restriction? I'm desperate, so I welcome ANY suggestions. Thanks!

302 tables? Define "extremely large"? # columns? Are they
normalized? What kind of data are you collecting? I have never used
more than about 70 columns in a single, and that was for a clinical
database. If you are using ASP to collect the data, you can write
different fields on your page to different tables... there's nothing
that says you have to write them all to a single one.

so more information please. What big "thing" is your database
describing? I would be willing to wager that you need to restructure.