Once a week corrupt data mdb on server :o(

[MS Access Codeman]

Hi,

i could use some suggestions on the following problem.

I wrote a MS Access 2003 application that is used on an network
with four workstations. The data mdb is on the server. The application
mde is running local on every workstation, two of witch are using MS
Access 2003 and the other two MS Access 2003 Runtime. There is a lot
of data entry, mostly in one table. In my test environment the
application runs fine and so it does most of the time in the network.

Only, approximatly once a week, the data mdb on the server gives a
problem. Suddenly all four users are getting a message the an object
cannot be found or is spelled wrong. I found a solution for this by
Compacting and Reparing the data mdb. After that the data mdb contains
a new table called MSysCompactError with a single record.

It says
Error code -1003
Cannot find field "Description"
Error Table "tblPostings"

The table tblPostings does not have a field named Description, i think
it refers to the descripion item belonging to a field definition of
the table. Also the table contains a record with illegal data like
#### for text fields and missing value for a autonumber field. I can
manualy delete this record. After that all users can start their MS
Access Application and use it without a problem. After 7 to 10 days
the process starts all over again, error message, compact/repair,
delete one erronious record and start again. Always on the same table,
always the same error.

Does anyone have a suggestion on:
- how to determine whats going wrong so i could solve it?
- how to solve the problem described above?

Thanx a lot

 

[Wayne Morgan]

It sounds as if you have a problem with the connection to the back-end file.
This could be an improper shutdown of Access or Windows on one of the
workstations or it could be a network problem. If the server and hubs aren't
on battery backups, they should be (good idea for the workstations also, but
a MUST for the server and hubs). If you're using a wireless network, don't.
After that, you will have to start trouble shooting the connections. If you
are getting improper shutdowns, the user should know about it and tell you
when you ask them.

 

[Tony Toews]

It says
Error code -1003
Cannot find field "Description"
Error Table "tblPostings"

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

For more information on corruption including possible causes,
determining the offending PC, retrieving your data, links, official MS
KB articles and a list of vendors who state they can fix corruption
see the Microsoft Access Corruption FAQ at
http://www.granite.ab.ca/access/corruptmdbs.htm

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

 

[eyal]

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

For more information on corruption including possible causes,
determining the offending PC, retrieving your data, links, official MS
KB articles and a list of vendors who state they can fix corruption
see the Microsoft Access Corruption FAQ at
http://www.granite.ab.ca/access/corruptmdbs.htm

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