Reserved error (-1038) when Updating > 109 fields in Access 2000/ SQL7

I have a table with 150 fields, and I'm importing data from a linked dBase table into a linked ODBC
SQL7 table (tried file dsn and machine dsn).

I created recordsets for the fields in both tables, and when I set the [SQL_field] = [dBase_Field]
on fewer than 109 fields, it Updates fine.  But Updating after the 109th field causes an error:
"Reserved error (-1038); there is no message for this error"

KB has a reference to this error number, but this is an Access 2000 program and never was in Access
97, nor was it ever replicated, so that article is useless (but the error message is identical).

This happens on several machines.

I have:
SQL 7
Access 2000 (Developer)
msjet40.dll  version 4.0.3714.7
windows 2000 pro

Any ideas what is causing this error???  Thanks!
DavidWareAsked:
Who is Participating?
I wear a lot of hats...

"The solutions and answers provided on Experts Exchange have been extremely helpful to me over the last few years. I wear a lot of hats - Developer, Database Administrator, Help Desk, etc., so I know a lot of things but not a lot about one thing. Experts Exchange gives me answers from people who do know a lot about one thing, in a easy to use platform." -Todd S.

Brendt HessSenior DBACommented:
How large is the total record size involved?  Is it possibly > 8000 bytes?
0

Experts Exchange Solution brought to you by

Your issues matter to us.

Facing a tech roadblock? Get the help and guidance you need from experienced professionals who care. Ask your question anytime, anywhere, with no hassle.

Start your 7-day free trial
DavidWareAuthor Commented:
I don't know how to find that out how large the total record size is.  Can I put in a Message box?
But here is further info.
At the customer's location, I ran this update with no problem.  It did not return any errors.
So there is something "wrong" with my installation, or something.
I am usually bedeviled by permissions and such - could it be something with that?
Thanks alot.
0
DavidWareAuthor Commented:
Hi bhess,
I decided to break the import into 2 halves.
Thanks for the help!
0
It's more than this solution.Get answers and train to solve all your tech problems - anytime, anywhere.Try it for free Edge Out The Competitionfor your dream job with proven skills and certifications.Get started today Stand Outas the employee with proven skills.Start learning today for free Move Your Career Forwardwith certification training in the latest technologies.Start your trial today
Microsoft SQL Server

From novice to tech pro — start learning today.

Question has a verified solution.

Are you are experiencing a similar issue? Get a personalized answer when you ask a related question.

Have a better answer? Share it in a comment.