too many fields defined

[Modest Marsupial]

I keep getting a run-time error that 'too many fields are defined' (it
thinks there is more than 255, even when there is not). I looked this
problem up at
http://www.microsoft-accesssolutions...ds_defined.htm which
explained it somewhat, but their simple solution of compacting the database
does not help me avoid this error. Their other solution of normalizing the
database to the third normal form is not practical for me (the database
isn't my creation to begin with and I'm very short on time).

I am wondering if others get this error and what they do about it.

Thanks in advance, marie

[Rick Brandt]

"Modest Marsupial" <Ma*******@mbg.com> wrote in message
news:10*************@corp.supernews.com...

I keep getting a run-time error that 'too many fields are defined' (it
thinks there is more than 255, even when there is not). I looked this
problem up at
http://www.microsoft-accesssolutions...ds_defined.htm which explained it somewhat, but their simple solution of compacting the database does not help me avoid this error. Their other solution of normalizing the database to the third normal form is not practical for me (the database
isn't my creation to begin with and I'm very short on time).

I am wondering if others get this error and what they do about it.

In addition to the hard limit on the number of fields you can also get this
if the total size of a row exceeds a certain number of bytes (forget how
many specifically).

Not much you can do about it except break the table up.

--
I don't check the Email account attached
to this message. Send instead to...
RBrandt at Hunter dot com

[Bas Cost Budde]

Modest Marsupial wrote:

I keep getting a run-time error that 'too many fields are defined' (it
thinks there is more than 255, even when there is not). I looked this
problem up at
http://www.microsoft-accesssolutions...ds_defined.htm which
explained it somewhat, but their simple solution of compacting the database
does not help me avoid this error. Their other solution of normalizing the
database to the third normal form is not practical for me (the database
isn't my creation to begin with and I'm very short on time).

I am wondering if others get this error and what they do about it.

Thanks in advance, marie

Does it go away if you copy the table, delete the original and rename
the copy? This can be awful if you have many relationships on the table...

--
Bas Cost Budde, Holland
http://www.heuveltop.nl/BasCB/msac_index.html
I prefer human mail above automated so in my address
replace the queue with a tea

[Modest Marsupial]

But the tables aren't too big (less than 100 rows). That's what's driving me
crazy. I can't see what is causing Access to think there's something bigger
than there is.

Thanks for the reply.
marie
"Rick Brandt" <ri*********@hotmail.com> wrote in message
news:32*************@individual.net...

"Modest Marsupial" <Ma*******@mbg.com> wrote in message
news:10*************@corp.supernews.com...

I keep getting a run-time error that 'too many fields are defined' (it
thinks there is more than 255, even when there is not). I looked this
problem up at
http://www.microsoft-accesssolutions...ds_defined.htm

which

explained it somewhat, but their simple solution of compacting the

database

does not help me avoid this error. Their other solution of normalizing

the

database to the third normal form is not practical for me (the database
isn't my creation to begin with and I'm very short on time).

I am wondering if others get this error and what they do about it.

In addition to the hard limit on the number of fields you can also get
this
if the total size of a row exceeds a certain number of bytes (forget how
many specifically).

Not much you can do about it except break the table up.

--
I don't check the Email account attached
to this message. Send instead to...
RBrandt at Hunter dot com

[Modest Marsupial]

Bas Cost Budde,

It's a recordset that I'm using (kind of as an array ...I'm a C programmer,
so these "recordsets" are new to me), not a table. Should this matter?

Thanks for the reply,
marie
"Bas Cost Budde" <b.*********@heuvelqop.nl> wrote in message
news:cp*********@news2.solcon.nl...

Modest Marsupial wrote:

I keep getting a run-time error that 'too many fields are defined' (it
thinks there is more than 255, even when there is not). I looked this
problem up at
http://www.microsoft-accesssolutions...ds_defined.htm
which explained it somewhat, but their simple solution of compacting the
database does not help me avoid this error. Their other solution of
normalizing the database to the third normal form is not practical for me
(the database isn't my creation to begin with and I'm very short on
time).

I am wondering if others get this error and what they do about it.

Thanks in advance, marie

Does it go away if you copy the table, delete the original and rename the
copy? This can be awful if you have many relationships on the table...

--
Bas Cost Budde, Holland
http://www.heuveltop.nl/BasCB/msac_index.html
I prefer human mail above automated so in my address
replace the queue with a tea

[Rick Brandt]

"Modest Marsupial" <Ma*******@mbg.com> wrote in message
news:10*************@corp.supernews.com...

But the tables aren't too big (less than 100 rows). That's what's driving me
crazy. I can't see what is causing Access to think there's something bigger
than there is.

What I said is that there is a size (bytes) limit *per row*. The number of rows
is irrelevant.

--
I don't check the Email account attached
to this message. Send instead to...
RBrandt at Hunter dot com

[Bas Cost Budde]

Modest Marsupial wrote:

Bas Cost Budde,

It's a recordset that I'm using (kind of as an array ...I'm a C programmer,
so these "recordsets" are new to me), not a table. Should this matter?

A recordset is an object; it enables data access. It has a source that
is either a table or some query returning records. Other database
systems call such an object a cursor, maybe that term runs associations
with you?

You can consider a recordset an array, to some extent. It will have an
item for every field in the record; it is close to two-dimensional in
the sense that you have more records in the recordset, but can address
only one at a time.

The Name property of the recordset will show you how it was created,
i.e. on a table, query (as saved object) or a SQL statement. You can
then inspect the structure of that source.

->Could a crosstab query yield too many fields?

--
Bas Cost Budde, Holland
http://www.heuveltop.nl/BasCB/msac_index.html
I prefer human mail above automated so in my address
replace the queue with a tea