A Microsoft Office (Excel, Word) forum. OfficeFrustration

If this is your first visit, be sure to check out the FAQ by clicking the link above. You may have to register before you can post: click the register link above to proceed. To start viewing messages, select the forum that you want to visit from the selection below.

Go Back   Home » OfficeFrustration forum » Microsoft Access » Database Design
Site Map Home Register Authors List Search Today's Posts Mark Forums Read  

Maximum fields in table problem



 
 
Thread Tools Display Modes
  #11  
Old July 31st, 2008, 02:02 AM posted to microsoft.public.access.tablesdbdesign
tygrus _
external usenet poster
 
Posts: 1
Default Maximum fields in table problem

Access has a problem when you change fields (name, datatype, number) in a large table. It cannot have more than 255 fields in a transaction. So if you have 200 fields then change 100 fields you have 300 fields in the transaction which exceeds the 255 limit.
If you have 200 fields already you cannot change more than 55 of them at a time. So change 50, (close design) save, (open design) and change another 50 fields .. and repeat.
Just for backup of Excel .. better to copy sheets elsewhere or wnole files to an archive.
Saving transactional data for summary .. start transaction in database, create Excel file with intial data, save link in Access database, action (eg. button) in Access or Excel file to update data in Access with final figures.

You could create separate tables for different portions of the Excel worksheet with a unique identifier for reference (you can't put 200+200 fields in a query but could process them sequentially).
 




Thread Tools
Display Modes

Posting Rules
You may not post new threads
You may not post replies
You may not post attachments
You may not edit your posts

vB code is On
Smilies are On
[IMG] code is Off
HTML code is Off
Forum Jump


All times are GMT +1. The time now is 12:22 PM.


Powered by vBulletin® Version 3.6.4
Copyright ©2000 - 2024, Jelsoft Enterprises Ltd.
Copyright ©2004-2024 OfficeFrustration.
The comments are property of their posters.