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  

"Too many fields defined"



 
 
Thread Tools Display Modes
  #1  
Old June 21st, 2007, 11:27 PM posted to microsoft.public.access.tablesdbdesign
S. Spencer
external usenet poster
 
Posts: 1
Default "Too many fields defined"

I keep getting the above error message. It supposedly means that I am trying
to exceed 255 fields but I only have 212 fields. Any suggestions?
  #2  
Old June 21st, 2007, 11:44 PM posted to microsoft.public.access.tablesdbdesign
fredg
external usenet poster
 
Posts: 4,386
Default "Too many fields defined"

On Thu, 21 Jun 2007 15:27:02 -0700, S. Spencer wrote:

I keep getting the above error message. It supposedly means that I am trying
to exceed 255 fields but I only have 212 fields. Any suggestions?


Any table with anything even approaching 100 fields, let alone 212
fields, would appear to be un-normalized.
Access is not a spreadsheet.

Post back with more detail's about your table structure and why you
think you need that many fields in one table.
--
Fred
Please respond only to this newsgroup.
I do not reply to personal e-mail
  #3  
Old June 21st, 2007, 11:59 PM posted to microsoft.public.access.tablesdbdesign
S. Spencer[_2_]
external usenet poster
 
Posts: 3
Default "Too many fields defined"

I am setting up a Master Table to be converted to Foundation specific
program. This is the culmination of all the tables that I maintain for our
organization but the company doing the conversion need the information in one
table.

"fredg" wrote:

On Thu, 21 Jun 2007 15:27:02 -0700, S. Spencer wrote:

I keep getting the above error message. It supposedly means that I am trying
to exceed 255 fields but I only have 212 fields. Any suggestions?


Any table with anything even approaching 100 fields, let alone 212
fields, would appear to be un-normalized.
Access is not a spreadsheet.

Post back with more detail's about your table structure and why you
think you need that many fields in one table.
--
Fred
Please respond only to this newsgroup.
I do not reply to personal e-mail

  #4  
Old June 22nd, 2007, 12:07 AM posted to microsoft.public.access.tablesdbdesign
Douglas J. Steele
external usenet poster
 
Posts: 9,313
Default "Too many fields defined"

While I agree with Fred that no table should have that many fields, try
compacting the database.

Are you sure you have to create a table for the company doing the
conversion? Can you just provide them with a query that joins everything
together?

--
Doug Steele, Microsoft Access MVP
http://I.Am/DougSteele
(no private e-mails, please)


"S. Spencer" S. wrote in message
...
I keep getting the above error message. It supposedly means that I am
trying
to exceed 255 fields but I only have 212 fields. Any suggestions?



  #5  
Old June 22nd, 2007, 12:19 AM posted to microsoft.public.access.tablesdbdesign
S. Spencer[_2_]
external usenet poster
 
Posts: 3
Default "Too many fields defined"

I am researching that but when we had our conference call with them, I
explained what I had very carefully (or so I thought). I was told that they
needed all the information that we wanted converted in one table to make the
conversion clean. I will try the compacting and repair for now.

Thank You!

"Douglas J. Steele" wrote:

While I agree with Fred that no table should have that many fields, try
compacting the database.

Are you sure you have to create a table for the company doing the
conversion? Can you just provide them with a query that joins everything
together?

--
Doug Steele, Microsoft Access MVP
http://I.Am/DougSteele
(no private e-mails, please)


"S. Spencer" S. wrote in message
...
I keep getting the above error message. It supposedly means that I am
trying
to exceed 255 fields but I only have 212 fields. Any suggestions?




  #6  
Old June 22nd, 2007, 03:40 AM posted to microsoft.public.access.tablesdbdesign
John W. Vinson
external usenet poster
 
Posts: 18,261
Default "Too many fields defined"

On Thu, 21 Jun 2007 16:19:01 -0700, S. Spencer
wrote:

I am researching that but when we had our conference call with them, I
explained what I had very carefully (or so I thought). I was told that they
needed all the information that we wanted converted in one table to make the
conversion clean.


They may be using the term "table" in a more generic sense than Access does.

Certainly you need all 212 (hopefully not more than 255!) fields in the same
recordset, or the same exported file, or in some form which is usable by the
other program.

It's not obvious that they must be within the same Access Table object in
order to do so, since Access Queries look, act, feel, export, etc. just like
tables in most circumstances.

Be sure it's not just a conflict of jargon!

John W. Vinson [MVP]
  #7  
Old June 22nd, 2007, 11:35 AM posted to microsoft.public.access.tablesdbdesign
scubadiver
external usenet poster
 
Posts: 1,673
Default "Too many fields defined"


This maybe enlightening:

http://www.mvps.org/access/tables/tbl0002.htm



"S. Spencer" wrote:

I keep getting the above error message. It supposedly means that I am trying
to exceed 255 fields but I only have 212 fields. Any suggestions?

  #8  
Old June 22nd, 2007, 08:59 PM posted to microsoft.public.access.tablesdbdesign
S. Spencer[_2_]
external usenet poster
 
Posts: 3
Default "Too many fields defined"

Thanks to everyone for their assistance. I believe that it's a communication
issue between myself and the consultant. I did compact and repair the Master
Table and it did the trick. However, we are trying to get some "face-time"
with this company so that they can better understand what I mean when I say
table vs database.

Thank you again.

"scubadiver" wrote:


This maybe enlightening:

http://www.mvps.org/access/tables/tbl0002.htm



"S. Spencer" wrote:

I keep getting the above error message. It supposedly means that I am trying
to exceed 255 fields but I only have 212 fields. Any suggestions?

  #9  
Old June 25th, 2007, 09:59 AM posted to microsoft.public.access.tablesdbdesign
Tom Wickerqueer
external usenet poster
 
Posts: 37
Default "Too many fields defined"

if you've seen this message then you shoudl move to SQL Server and Access
Data Projects



"S. Spencer" S. wrote in message
...
I keep getting the above error message. It supposedly means that I am
trying
to exceed 255 fields but I only have 212 fields. Any suggestions?


  #10  
Old June 25th, 2007, 01:14 PM posted to microsoft.public.access.tablesdbdesign
BruceM[_2_]
external usenet poster
 
Posts: 1,763
Default "Too many fields defined"

Ignore this bitter troll. He shows up from time to time to advocate ADP as
the cure to all problems. Sad to say, when he shows up it tends to last for
a while until he becomes bored or something.

"Tom Wickerqueer" wrote in message
...
if you've seen this message then you shoudl move to SQL Server and Access
Data Projects



"S. Spencer" S. wrote in message
...
I keep getting the above error message. It supposedly means that I am
trying
to exceed 255 fields but I only have 212 fields. Any suggestions?




 




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 03:15 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.