"Can't find field 'Description'"

  • Thread starter Thread starter Guest
  • Start date Start date
G

Guest

We use Access 2000 with SQL 7 back end. All has been working fine but
suddenly we are getting the error message "Can't find field 'Description'"
when the database is shutting down. I verified that only the database window
was open at the time the database was being shut down so where is this error
coming from? I have the front end set to compact/repair on shut down and this
error causes a db1, db2, etc to be created. The problem is not limited to a
single database but it does appear to be limited to specific computers. Any
ideas someone can offer would be greatly appreciated as I'm stumped.
 
jkmccnh said:
We use Access 2000 with SQL 7 back end. All has been working fine but
suddenly we are getting the error message "Can't find field 'Description'"
when the database is shutting down. I verified that only the database window
was open at the time the database was being shut down so where is this error
coming from?
Click to expand...

The official problem description of that error message is the
following:

1017 - "Could not find field "Description" It's possible the problem
is with a table that has a self-join and Memo fields, and has
referential integrity enforced. ACC2000: Table Corruption After
Referential Integrity Checks - 296389
http://support.microsoft.com/?kbid=296389 But it's more likely to be a
sign of corruption

You state a SQL 7 backend but do you have any tables in the MDB? What
happens when you import the contents of the MDB into a new MDB?

Tony
--
Tony Toews, Microsoft Access MVP
Please respond only in the newsgroups so that others can
read the entire thread of messages.
Microsoft Access Links, Hints, Tips & Accounting Systems at
http://www.granite.ab.ca/accsmstr.htm
 
There are both local and linked tables, but no self joins. The error occurs
on the specific computer because if I use the db in question (through a
shared folder as an admin) the db shuts down fine and doesn't give the error.
When I go back to the actual station, open the db, then shut it down without
opening anything except the db window the error occurs again. Also, the error
happens on multiple databases that are used at the workstation. It's very
strange. Could something within the local copy of Access be corrupt and cause
the error rather than something within a specific db? Because I can open and
close the db's (through a shared folder) and they work fine I haven't tried
importing objects into a new "shell". Thanks for your help.
 
jkmccnh said:
There are both local and linked tables, but no self joins. The error occurs
on the specific computer because if I use the db in question (through a
shared folder as an admin) the db shuts down fine and doesn't give the error.
When I go back to the actual station, open the db, then shut it down without
opening anything except the db window the error occurs again. Also, the error
happens on multiple databases that are used at the workstation. It's very
strange. Could something within the local copy of Access be corrupt and cause
the error rather than something within a specific db? Because I can open and
close the db's (through a shared folder) and they work fine I haven't tried
importing objects into a new "shell".
Click to expand...

Interesting problem. I'd wonder if those workstations are up to date
in terms of Office and Jet SPs.

I'm also unclear on what set of DLLs Access uses to hit SQL Server.
That is is MDAC in use in that situation? So just to be sure I'd
check the MDAC version too.

Tony
--
Tony Toews, Microsoft Access MVP
Please respond only in the newsgroups so that others can
read the entire thread of messages.
Microsoft Access Links, Hints, Tips & Accounting Systems at
http://www.granite.ab.ca/accsmstr.htm
 
Thanks, I'll have IT check into those.

Tony Toews said:
Interesting problem. I'd wonder if those workstations are up to date
in terms of Office and Jet SPs.

I'm also unclear on what set of DLLs Access uses to hit SQL Server.
That is is MDAC in use in that situation? So just to be sure I'd
check the MDAC version too.

Tony
--
Tony Toews, Microsoft Access MVP
Please respond only in the newsgroups so that others can
read the entire thread of messages.
Microsoft Access Links, Hints, Tips & Accounting Systems at
http://www.granite.ab.ca/accsmstr.htm
Click to expand...
 
Back
Top