G
Guest
Is the table column limit in Access 2003 still 255 as it is in Access 2000?
You are using an out of date browser. It may not display this or other websites correctly.
You should upgrade or use an alternative browser.
You should upgrade or use an alternative browser.
A
Allen Browne
Yes. Since that's about 4 times what you will ever need in a normalized
database, there is no need to change it.
--
Allen Browne - Microsoft MVP. Perth, Western Australia.
Reply to group, rather than allenbrowne at mvps dot org.
database, there is no need to change it.
--
Allen Browne - Microsoft MVP. Perth, Western Australia.
Reply to group, rather than allenbrowne at mvps dot org.
2000?dan0771 said:Is the table column limit in Access 2003 still 255 as it is in Access
G
Guest
I agree it should be plenty...the problem is I'm working with a legacy system built in Paradox where 2 table have close to 400 columns. As luck would have it, the 30 columns I need are past the 255 limit in Access. Is there any way to link to a table using an SQL script where it would just link the 30 columns I need (Link not Import)? Can Access link to a view?
B
Brendan Reynolds
You can link to a SQL Server view - it appears as a table to Access. Don't
know about Paradox, though. If you haven't tried it already, create your
view and try to link it in the same way that you would link a table. If the
feature is supported with Paradox as it is with SQL Server, you should see
the view listed along with the tables.
--
Brendan Reynolds (MVP)
would have it, the 30 columns I need are past the 255 limit in Access. Is
there any way to link to a table using an SQL script where it would just
link the 30 columns I need (Link not Import)? Can Access link to a view?
know about Paradox, though. If you haven't tried it already, create your
view and try to link it in the same way that you would link a table. If the
feature is supported with Paradox as it is with SQL Server, you should see
the view listed along with the tables.
--
Brendan Reynolds (MVP)
system built in Paradox where 2 table have close to 400 columns. As luckdan0771 said:I agree it should be plenty...the problem is I'm working with a legacy
would have it, the 30 columns I need are past the 255 limit in Access. Is
there any way to link to a table using an SQL script where it would just
link the 30 columns I need (Link not Import)? Can Access link to a view?
Can't get data from SQL Server table w/ 300+ columns
Said SQL Server table is from MICRSOFT's CRM system deployed by a Microsoft certified consultant. Hmmm. Maybe 300 isn't enough. Envision this, you have a construction site with many characteristics:
street address1
street address2
City
County
State
Zip
# units
# buildings
Permit Date
Permit agency
etc.
You can chew up 300 columns pretty quickly with the site ID forming a valid primary key with the only other candidate being the address (a 5-part key). That is 3rd normal form, Right? Sure, the address could be split into its own table but the CRM system doesn't make that easy. Then you could put all the permit stuff in another table but it would still be 1-1 and provide nothing but $$$$ for Microsoft consultants.
Anyway, Microsoft needs to quit bagging on DB's with 300 columns and provide a solution.
Said SQL Server table is from MICRSOFT's CRM system deployed by a Microsoft certified consultant. Hmmm. Maybe 300 isn't enough. Envision this, you have a construction site with many characteristics:
street address1
street address2
City
County
State
Zip
# units
# buildings
Permit Date
Permit agency
etc.
You can chew up 300 columns pretty quickly with the site ID forming a valid primary key with the only other candidate being the address (a 5-part key). That is 3rd normal form, Right? Sure, the address could be split into its own table but the CRM system doesn't make that easy. Then you could put all the permit stuff in another table but it would still be 1-1 and provide nothing but $$$$ for Microsoft consultants.
Anyway, Microsoft needs to quit bagging on DB's with 300 columns and provide a solution.