03-03-2016 03:03 PM
That's an Access limitation, right?
If so, there's nothing much SAS can do about that, technically.
You should consider your data structure. How can you even handle that many columns. Think of naming all those columns in a query etc...
Transpose and normalize your data. It will make it easier to use and maintain. Ans as a bonus, being able to export to Access :-)
03-03-2016 03:08 PM - edited 03-03-2016 03:09 PM
Access 2010 - 255 columns in a table.
Separate data into two tables that can be linked by an ID. Each table holding less than 255 columns.
03-04-2016 04:35 AM
As @LinusH has stated, structure your data correctly. Access is (a rather poor sibling to anyway), a Relational Database. What this means is that data elements only appear once, these distinct lists as simple to merge back together but are not stored in one table. Attached is a picture which shows an example. You will see that the data is split out into separate tables, each with links to other tables. This is what "relational" means, once they are merged together by the variables then you get the full data.
There are many reasons for this setup. I would suggest you read up on what a Relation Database is, and how your data should look:
For example as a starter.
Then plan out your database schema -> much like the picture attached, draw each table, what distinct values it will contain, how they link together, then its just a matter of processing your one dataset in SAS to create each of the required datasets, which in turn can then be inserted into the respective table in Access. Note that SAS is not a Relational Database, so the structure is slighty different.